Ultra-reliable low-latency communication indication channelization designs

ABSTRACT

In some circumstances, a URLLC may preempt resource. An apparatus may be configured to receive a set of resource blocks from a base station including at least one of eMBB data or URLLC data in a PDSCH. The apparatus may receive a URLLC indicator from the base station. The URLLC indicator may be received embedded within the URLLC data or received separate from the URLLC data within DCI of a PDCCH. The URLLC indicator indicates whether the set of resource blocks includes at least part of the URLLC data. The apparatus may determine, based on the URLLC indicator, whether the set of resource blocks includes the URLLC data and processing the set of resource blocks based on a result of determining whether the set of resource blocks includes the URLLC data.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a Continuation of U.S. application Ser. No.15/917,566, entitled “ULTRA-RELIABLE LOW-LATENCY COMMUNICATIONINDICATION CHANNELIZATION DESIGNS” and filed on Mar. 9, 2018 whichclaims the benefit of U.S. Provisional Application Ser. No. 62/470,075,entitled “ULTRA-RELIABLE LOW-LATENCY COMMUNICATION INDICATIONCHANNELIZATION DESIGNS” and filed on Mar. 10, 2017, both of which areexpressly incorporated by reference herein in their entirety.

BACKGROUND Technical Field

The present disclosure relates generally to communication systems, andmore particularly, to systems, methods, and devices that provide anindication of an occurrence of an ultra-reliable low-latencycommunication.

Introduction

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources. Examples of suchmultiple-access technologies include code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example telecommunication standardis 5G New Radio (NR). 5G NR is part of a continuous mobile broadbandevolution promulgated by Third Generation Partnership Project (3GPP) tomeet new requirements associated with latency, reliability, security,scalability (e.g., with Internet of Things (IoT)), and otherrequirements. Some aspects of 5G NR may be based on the 4G Long TermEvolution (LTE) standard. There exists a need for further improvementsin 5G NR technology. These improvements may also be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

In some circumstances, an ultra-reliable low-latency communication(URLLC) may preempt or puncture resources occupied by, for example, anongoing enhanced mobile broadband (eMBB) communication. Accordingly,some devices may send a URLLC indicator indicating that the URLLC datais within an eMBB data. Other devices may receive a URLLC indicatorindicating that the URLLC data is within an eMBB data.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

As discussed above, in some circumstances, a URLLC may preempt orpuncture a resource occupied by, for example, an ongoing eMBBcommunication. For example, the URLLC may take the place of a portion ofeMBB data in the, for example, ongoing eMBB communication. In analternate example, the URLLC data may be sent at the same time as aportion of eMBB data, puncturing the portion of eMBB data, in theongoing eMBB communication.

Accordingly, some devices (e.g., a base station or a UE) may send aURLLC indicator indicating that the URLLC data is sent on shared channelresources which may include eMBB data. Other devices (e.g., a UE or abase station) may receive a URLLC indicator indicating that the URLLCdata is sent on the shared channel and may puncture or preempt the eMBBdata.

In an aspect of the disclosure, a method, a computer-readable medium,and an apparatus are provided. The apparatus may be a base stationconfigured to generate a set of resource blocks including at least oneof eMBB data or URLLC data in a physical downlink shared channel(PDSCH). The base station may be configured to generate a URLLCindicator indicating whether the set of resource blocks includes atleast part of the URLLC data. The base station may be configured tosend, to at least one user equipment (UE), the URLLC indicator and theset of resource blocks including the at least one of the eMBB data orthe URLLC data. The URLLC indicator being sent embedded within the URLLCdata or being sent separate from the URLLC data within downlink controlinformation (DCI) of a physical downlink control channel (PDCCH).

In another aspect of the disclosure, a method, a computer-readablemedium, and an apparatus are provided. The apparatus may be a UEconfigured to receive a set of resource blocks from a base stationcomprising at least one of eMBB data or URLLC data in a PDSCH. The UEmay be configured to receive a URLLC indicator from the base station.The URLLC indicator may be received embedded within the URLLC data orbeing received separate from the URLLC data within DCI of a PDCCH. TheURLLC indicator may indicate whether the set of resource blocks includesthe URLLC data. The UE may be configured to determine, based on theURLLC indicator, whether the set of resource blocks includes the URLLCdata. The UE may be configured to processing, based on the URLLCindicator, the received set of resource blocks including the at leastone of the eMBB data or the URLLC data.

In another aspect of the disclosure, a method, a computer-readablemedium, and an apparatus are provided. The apparatus may be a UEconfigured to generate a set of resource blocks including URLLC data,generate a URLLC indicator in a group-common DCI message indicating thatthe URLLC data is in a subset of the set of resource blocks and iswithin the PUSCH for eMBB data, and sending, to a base station, theURLLC indicator and the set of resource blocks including the URLLC data.

In another aspect of the disclosure, a method, a computer-readablemedium, and an apparatus are provided. The apparatus may be a basestation configured to receive a set of resource blocks from a UE. The UEmay also be configured to receive a URLLC indicator from the basestation (gNB). Additionally, the UE may be configured to determine,based on the URLLC indicator, that a subset of the set of resourceblocks includes or does not include URLLC data.

In another aspect of the disclosure, a method, a computer-readablemedium, and an apparatus are provided. The apparatus may be a UEconfigured to transmit, to a base station, a URLLC indicator indicatinga set of uplink (UL) URLLC resources for transmitting URLLC data. The UEmay also be configured to generate a set of resource blocks includingURLLC data. Additionally, the UE may be configured to send, to the basestation, the set of resource blocks including the URLLC data within theindicated set of UL URLLC resources.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network.

FIGS. 2A, 2B, 2C, and 2D are diagrams illustrating examples of a DLsubframe, DL channels within the DL subframe, an UL subframe, and ULchannels within the UL subframe, respectively, for a 5G/NR framestructure.

FIG. 3 is a diagram illustrating an example of a base station and userequipment (UE) in an access network.

FIG. 4 is a diagram illustrating a base station in communication with aUE.

FIG. 5 is a diagram illustrating an example of a DL frame structure.

FIG. 6 is a diagram illustrating an example of a DL frame structure.

FIG. 7 is a diagram illustrating an example of a DL frame structure.

FIG. 8 is a diagram illustrating an example of a DL frame structure.

FIG. 9 is a diagram illustrating an example of a DL frame structure.

FIG. 10 is a diagram illustrating an example of a UL frame structure.

FIG. 11 is a diagram illustrating an example of a UL frame structure.

FIG. 12 is a flowchart of a method of wireless communication.

FIG. 13 is a flowchart of a method of wireless communication.

FIG. 14 is a flowchart of a method of wireless communication.

FIG. 15 is a flowchart of a method of wireless communication.

FIG. 16 is a flowchart of a method of wireless communication.

FIG. 17 is a flowchart of a method of wireless communication.

FIG. 18 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 19 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 20 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 21 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 22 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 23 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 24 is a conceptual data flow diagram illustrating the data flowbetween different means/components in an exemplary apparatus.

FIG. 25 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, components, circuits,processes, algorithms, etc. (collectively referred to as “elements”).These elements may be implemented using electronic hardware, computersoftware, or any combination thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented as a “processing system” thatincludes one or more processors. Examples of processors includemicroprocessors, microcontrollers, graphics processing units (GPUs),central processing units (CPUs), application processors, digital signalprocessors (DSPs), reduced instruction set computing (RISC) processors,systems on a chip (SoC), baseband processors, field programmable gatearrays (FPGAs), programmable logic devices (PLDs), state machines, gatedlogic, discrete hardware circuits, and other suitable hardwareconfigured to perform the various functionality described throughoutthis disclosure. One or more processors in the processing system mayexecute software. Software shall be construed broadly to meaninstructions, instruction sets, code, code segments, program code,programs, subprograms, software components, applications, softwareapplications, software packages, routines, subroutines, objects,executables, threads of execution, procedures, functions, etc., whetherreferred to as software, firmware, middleware, microcode, hardwaredescription language, or otherwise.

Accordingly, in one or more example embodiments, the functions describedmay be implemented in hardware, software, or any combination thereof. Ifimplemented in software, the functions may be stored on or encoded asone or more instructions or code on a computer-readable medium.Computer-readable media includes computer storage media. Storage mediamay be any available media that can be accessed by a computer. By way ofexample, and not limitation, such computer-readable media can comprise arandom-access memory (RAM), a read-only memory (ROM), an electricallyerasable programmable ROM (EEPROM), optical disk storage, magnetic diskstorage, other magnetic storage devices, combinations of theaforementioned types of computer-readable media, or any other mediumthat can be used to store computer executable code in the form ofinstructions or data structures that can be accessed by a computer.

Various aspects of the systems and methods described herein relate touplink or downlink indications. The uplink or downlink indications maybe URLLC indications, i.e., a URLLC indicator. Accordingly, in someaspects, the URLLC indicator may be an uplink URLLC indicator and inother aspects, the URLLC indicator may be a downlink URLLC indicator.The downlink indicator may be transmitted from a base station to a UE.The uplink indicator may be transmitted from a UE to a base station. Inan aspect, a downlink indicator may be in DCI of a group common PDCCH. Adownlink indicator may be a post indication, e.g., appearing at thestart of a next slot. Additionally, a downlink indicator may beconfigured to be a wideband indication or a sub-band indication (e.g.,up to 2 sub-bands) indication. For example, the downlink indicator mayindicate that a URLCC will preempt or puncture an entire band, which maybe referred to as wideband or preempt or puncture a sub-band, which maybe referred to as sub-band. In some instances, the downlink indicatormay indicate that a URLCC will preempt or puncture an entire band, whilethe actual data send may not take up the entire band. Furthermore, adownlink indicator may be configured to indicate one or more symbols byconfiguring the monitoring periodicity. In an aspect, a uplink indicatormay use one or more of the formats described herein with respect todownlink indicators. In some aspects, a downlink indicator may be acurrent indication, e.g., appearing in the same symbols or mini-slots asthe URLLC data. In one example, the indicator may be embedded in theURLLC data. In another example, the indicator may be separate from theURLLC data. In some aspects, a downlink indicator may be apre-indication, e.g., appearing before the URLLC data. In one example,the indicator may be transmitted in the beginning of the slot, e.g., inDCI of a group common PDCCH followed by the URLLC data.

FIG. 1 is a diagram illustrating an example of a wireless communicationssystem and an access network 100. The wireless communications system(also referred to as a wireless wide area network (WWAN)) includes basestations 102, UEs 104, and an Evolved Packet Core (EPC) 160. The basestations 102 may include macro cells (high power cellular base station)and/or small cells (low power cellular base station). The macro cellsinclude base stations. The small cells include femtocells, picocells,and microcells.

The base stations 102 (collectively referred to as Evolved UniversalMobile Telecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN)) interface with the EPC 160 through backhaul links 132 (e.g.,S1 interface). In addition to other functions, the base stations 102 mayperform one or more of the following functions: transfer of user data,radio channel ciphering and deciphering, integrity protection, headercompression, mobility control functions (e.g., handover, dualconnectivity), inter-cell interference coordination, connection setupand release, load balancing, distribution for non-access stratum (NAS)messages, NAS node selection, synchronization, radio access network(RAN) sharing, multimedia broadcast multicast service (MBMS), subscriberand equipment trace, RAN information management (RIM), paging,positioning, and delivery of warning messages. The base stations 102 maycommunicate directly or indirectly (e.g., through the EPC 160) with eachother over backhaul links 134 (e.g., X2 interface). The backhaul links134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Eachof the base stations 102 may provide communication coverage for arespective geographic coverage area 110. There may be overlappinggeographic coverage areas 110. For example, the small cell 102′ may havea coverage area 110′ that overlaps the coverage area 110 of one or moremacro base stations 102. A network that includes both small cell andmacro cells may be known as a heterogeneous network. A heterogeneousnetwork may also include Home Evolved Node Bs (eNBs) (HeNBs), which mayprovide service to a restricted group known as a closed subscriber group(CSG). The communication links 120 between the base stations 102 and theUEs 104 may include uplink (UL) (also referred to as reverse link)transmissions from a UE 104 to a base station 102 and/or downlink (DL)(also referred to as forward link) transmissions from a base station 102to a UE 104. The communication links 120 may use multiple-input andmultiple-output (MIMO) antenna technology, including spatialmultiplexing, beamforming, and/or transmit diversity. The communicationlinks may be through one or more carriers. The base stations 102/UEs 104may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100 MHz) bandwidthper carrier allocated in a carrier aggregation of up to a total of YxMHz (x component carriers) used for transmission in each direction. Thecarriers may or may not be adjacent to each other. Allocation ofcarriers may be asymmetric with respect to DL and UL (e.g., more or lesscarriers may be allocated for DL than for UL). The component carriersmay include a primary component carrier and one or more secondarycomponent carriers. A primary component carrier may be referred to as aprimary cell (PCell) and a secondary component carrier may be referredto as a secondary cell (SCell).

Certain UEs 104 may communicate with each other using device-to-device(D2D) communication link 192. The D2D communication link 192 may use theDL/UL WWAN spectrum. The D2D communication link 192 may use one or moresidelink channels, such as a physical sidelink broadcast channel(PSBCH), a physical sidelink discovery channel (PSDCH), a physicalsidelink shared channel (PSSCH), and a physical sidelink control channel(PSCCH). D2D communication may be through a variety of wireless D2Dcommunications systems, such as for example, FlashLinQ, WiMedia,Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi accesspoint (AP) 150 in communication with Wi-Fi stations (STAs) 152 viacommunication links 154 in a 5 GHz unlicensed frequency spectrum. Whencommunicating in an unlicensed frequency spectrum, the STAs 152/AP 150may perform a clear channel assessment (CCA) prior to communicating inorder to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensedfrequency spectrum. When operating in an unlicensed frequency spectrum,the small cell 102′ may employ NR and use the same 5 GHz unlicensedfrequency spectrum as used by the Wi-Fi AP 150. The small cell 102′,employing NR in an unlicensed frequency spectrum, may boost coverage toand/or increase capacity of the access network.

The gNodeB (gNB) 180 may operate in millimeter wave (mmW) frequenciesand/or near mmW frequencies in communication with the UE 104. When thegNB 180 operates in mmW or near mmW frequencies, the gNB 180 may bereferred to as an mmW base station. Extremely high frequency (EHF) ispart of the RF in the electromagnetic spectrum. EHF has a range of 30GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters.Radio waves in the band may be referred to as a millimeter wave. NearmmW may extend down to a frequency of 3 GHz with a wavelength of 100millimeters. The super high frequency (SHF) band extends between 3 GHzand 30 GHz, also referred to as centimeter wave. Communications usingthe mmW/near mmW radio frequency band has extremely high path loss and ashort range. The mmW base station 180 may utilize beamforming 184 withthe UE 104 to compensate for the extremely high path loss and shortrange.

The EPC 160 may include a Mobility Management Entity (MME) 162, otherMMES 164, a Serving Gateway 166, a Multimedia Broadcast MulticastService (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC)170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be incommunication with a Home Subscriber Server (HSS) 174. The MME 162 isthe control node that processes the signaling between the UEs 104 andthe EPC 160. Generally, the MME 162 provides bearer and connectionmanagement. All user Internet protocol (IP) packets are transferredthrough the Serving Gateway 166, which itself is connected to the PDNGateway 172. The PDN Gateway 172 provides UE IP address allocation aswell as other functions. The PDN Gateway 172 and the BM-SC 170 areconnected to the IP Services 176. The IP Services 176 may include theInternet, an intranet, an IP Multimedia Subsystem (IMS), a PS StreamingService (PSS), and/or other IP services. The BM-SC 170 may providefunctions for MBMS user service provisioning and delivery. The BM-SC 170may serve as an entry point for content provider MBMS transmission, maybe used to authorize and initiate MBMS Bearer Services within a publicland mobile network (PLMN), and may be used to schedule MBMStransmissions. The MBMS Gateway 168 may be used to distribute MBMStraffic to the base stations 102 belonging to a Multicast BroadcastSingle Frequency Network (MBSFN) area broadcasting a particular service,and may be responsible for session management (start/stop) and forcollecting eMBMS related charging information.

The base station may also be referred to as a gNB, Node B, evolved NodeB (eNB), an access point, a base transceiver station, a radio basestation, a radio transceiver, a transceiver function, a basic serviceset (BSS), an extended service set (ESS), or some other suitableterminology. The base station 102 provides an access point to the EPC160 for a UE 104. Examples of UEs 104 include a cellular phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personaldigital assistant (PDA), a satellite radio, a global positioning system,a multimedia device, a video device, a digital audio player (e.g., MP3player), a camera, a game console, a tablet, a smart device, a wearabledevice, a vehicle, an electric meter, a gas pump, a large or smallkitchen appliance, a healthcare device an implant, a display, or anyother similar functioning device. Some of the UEs 104 may be referred toas IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heartmonitor, etc.). The UE 104 may also be referred to as a station, amobile station, a subscriber station, a mobile unit, a subscriber unit,a wireless unit, a remote unit, a mobile device, a wireless device, awireless communications device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a user agent, a mobile client, a client, orsome other suitable terminology.

Referring again to FIG. 1, in certain aspects, the base station 102 maybe configured to generate a set of resource blocks including at leastone of eMBB data or URLLC data in a PDSCH. The base station 102 may alsobe configured to generate a URLLC indicator indicating whether the setof resource blocks includes at least part of the URLLC data.Additionally, the base station 102 may be configured to send, to atleast one user equipment (UE), the URLLC indicator and the set ofresource blocks including the at least one of the eMBB data or the URLLCdata, the URLLC indicator being sent embedded within the URLLC data orbeing sent separate from the URLLC data within downlink controlinformation (DCI) of a physical downlink control channel (PDCCH) (198).

Accordingly, the UE 104 may be configured to receive a set of resourceblocks from a base station comprising at least one of eMBB data or URLLCdata in a PDSCH. The UE 104 may also be configured to receiving a URLLCindicator from the base station, the URLLC indicator being receivedembedded within the URLLC data or being received separate from the URLLCdata within DCI of a PDCCH, the URLLC indicator indicating whether theset of resource blocks includes at least part of the URLLC data. Whenthe URLLC data is embedded in the eMBB data, the URLLC may preempt eMBBtransmissions on the same resources such that only the URLLC data istransmitted on the embedded resource and eMBB transmissions are omittedor canceled. In addition, the UE 104 may determine, based on the URLLCindicator, whether the set of resource blocks includes the URLLC dataand processing the set of resource blocks based on a result ofdetermining whether the set of resource blocks includes the URLLC data(199).

From the perspective of a URLLC device, generally, the URLLC device maynot know or may not care about other UEs' (e.g., eMBB UEs) transmissionson PUSCH or PDSCH. Rather, a URLLC device may provide an indication thatthe URLLC device is prepared to transmit URLLC data on resourcesindicated by the URLLC indicator irrespective of other transmissionsthat may occupy those resources and which may be scheduled or ongoing.In an aspect, when a base station transmits a URLLC indicator, noscheduling is used. In another aspect, a UE may be the URLLC device, butthe base station may be used to transmit a URLLC indication.

From the perspective of an eMBB UE, the eMBB UE may have to deal withtransmissions on PUSCH from the URLLC device or transmissions to theURLLC device on PDSCH. The URLLC device may simply provide an indicationthat the URLLC device is prepared to transmit URLLC data on indicatedresources. The URLLC device may be a URLLC UE or a URLLC base station.Downlink interruptions due to URLLC data may be signaled by a downlinkURLLC indicator. In this case, if the URLLC data occupies resources thatare allocated to an eMBB UE (i.e., when the URLLC data is embedded inthe eMBB data), the eMBB UE may decode a DL transmission based on thisinformation. For example, the eMBB UE may determine that the URLLC datapunctures its DL transmission and may perform decoding of the DLtransmission punctured with URLLC based on this determination (e.g.,zeroing bits indicated as URLLC data). On the uplink, using the URLLCindicator, the eMBB UE may rate match its transmission of eMBB dataaround the resources occupied by URLLC data sent from an base station.

In an example, a URLLC device may identify the availability ofmini-slots for transmission of URLLC data in a set of one or moreresource blocks. The URLLC device may generate a first transmission on aPUSCH including URLLC data in at least one of the mini-slots. The URLLCdevice may generate a second transmission comprising a URLLC indicatorto signal the presence of the URLLC data in the at least one mini-slot.The URLLC device may send the first and second transmissions in the setof one or more resource blocks.

In an aspect, URLLC data may be transmitted in an uplink mini-slot whichmay be dynamically or semi-statically configured and which is identifiedto the base station by the URLLC indicator.

In an aspect, a URLCC device may send an indicator of URLLC data. Theindicator of the URLLC data may, in some examples, be sent regardless ofwhether URLLC data is present or not. For example, the URLLC indicatormay indicate that URLLC data is present and where the URLLC data islocated in a transmission. The URLLC indicator may also indicate that noURLLC data is present in a particular transmission. Thus, a URLLC devicemay transmit a URLLC indicator to another device, such as an eMBB UE.The other device may be required to monitor for the URLLC indicator todetermine if URLCC data is present and to then take appropriate actionwhen the URLLC data is present. For example, an eMBB UE may rate matcharound the URLLC data or zero out any received URLLC data base on theexistence of URLLC data as may be indicated by the URLCC indicator. In acase when the URLCC indicator indicates that no URLLC data, the otherdevice may do nothing. For example, the eMBB UE will not be required torate match any transmitted data around URLCC data or zero out anyreceived data. In other examples, URLLC indicators might be sent onlywhen URLLC data is present.

In some aspects, an indicator may be sent regardless of the presence ofURLLC data. For example, a URLLC indicator may be sent periodically. Inother aspects, a URLLC indicator may be sent only when URLLC data ispresent.

In some aspects, an indicator may be received regardless of the presenceof URLLC data. For example, a URLLC indicator may be receivedperiodically (having been sent periodically by a URLLC device). In otheraspects, a URLLC indicator may be received only when URLLC data ispresent.

FIG. 2A is a diagram 200 illustrating an example of a DL subframe withina 5G/NR frame structure. FIG. 2B is a diagram 230 illustrating anexample of channels within a DL subframe. FIG. 2C is a diagram 250illustrating an example of an UL subframe within a 5G/NR framestructure. FIG. 2D is a diagram 280 illustrating an example of channelswithin an UL subframe. The 5G/NR frame structure may be FDD in which fora particular set of subcarriers (carrier system bandwidth), subframeswithin the set of subcarriers are dedicated for either DL or UL, or maybe TDD in which for a particular set of subcarriers (carrier systembandwidth), subframes within the set of subcarriers are dedicated forboth DL and UL. In the examples provided by FIGS. 2A, 2C, the 5G/NRframe structure is assumed to be TDD, with subframe 4 a DL subframe andsubframe 7 an UL subframe. While subframe 4 is illustrated as providingjust DL and subframe 7 is illustrated as providing just UL, anyparticular subframe may be split into different subsets that provideboth UL and DL. Note that the description infra applies also to a 5G/NRframe structure that is FDD.

Other wireless communication technologies may have a different framestructure and/or different channels. A frame (10 ms) may be divided into10 equally sized subframes (1 ms). Each subframe may include one or moretime slots. Each slot may include 7 or 14 symbols, depending on the slotconfiguration. For slot configuration 0, each slot may include 14symbols, and for slot configuration 1, each slot may include 7 symbols.The number of slots within a subframe is based on the slot configurationand the numerology. For slot configuration 0, different numerologies 0to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe.For slot configuration 1, different numerologies 0 to 2 allow for 2, 4,and 8 slots, respectively, per subframe. The subcarrier spacing andsymbol length/duration are a function of the numerology. The subcarrierspacing may be equal to 2^(μ)*15 kKz, where μ is the numerology 0-5. Thesymbol length/duration is inversely related to the subcarrier spacing.FIGS. 2A, 2C provide an example of slot configuration 1 with 7 symbolsper slot and numerology 0 with 2 slots per subframe. The subcarrierspacing is 15 kHz and symbol duration is approximately 66.7 μs.

A resource grid may be used to represent the frame structure. Each timeslot includes a resource block (RB) (also referred to as physical RBs(PRBs)) that extends 12 consecutive subcarriers. The resource grid isdivided into multiple resource elements (REs). The number of bitscarried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot)signals (RS) for the UE (indicated as R). The RS may includedemodulation RS (DM-RS) and channel state information reference signals(CSI-RS) for channel estimation at the UE. The RS may also include beammeasurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS(PT-RS).

FIG. 2B illustrates an example of various channels within a DL subframeof a frame. The physical control format indicator channel (PCFICH) iswithin symbol 0 of slot 0, and carries a control format indicator (CFI)that indicates whether the PDCCH occupies 1, 2, or 3 symbols (FIG. 2Billustrates a PDCCH that occupies 3 symbols). The PDCCH carries DCIwithin one or more control channel elements (CCEs), each CCE includingnine RE groups (REGs), each REG including four consecutive REs in anOFDM symbol. A UE may be configured with a UE-specific enhanced PDCCH(ePDCCH) that also carries DCI. The ePDCCH may have 2, 4, or 8 RB pairs(FIG. 2B shows two RB pairs, each subset including one RB pair). Thephysical hybrid automatic repeat request (ARQ) (HARQ) indicator channel(PHICH) is also within symbol 0 of slot 0 and carries the HARQ indicator(HI) that indicates HARQ acknowledgement (ACK)/negative ACK (NACK)feedback based on the physical uplink shared channel (PUSCH). Theprimary synchronization channel (PSCH) may be within symbol 6 of slot 0within subframes 0 and 5 of a frame. The PSCH carries a primarysynchronization signal (PSS) that is used by a UE 104 to determinesubframe/symbol timing and a physical layer identity. The secondarysynchronization channel (SSCH) may be within symbol 5 of slot 0 withinsubframes 0 and 5 of a frame. The SSCH carries a secondarysynchronization signal (SSS) that is used by a UE to determine aphysical layer cell identity group number and radio frame timing. Basedon the physical layer identity and the physical layer cell identitygroup number, the UE can determine a physical cell identifier (PCI).Based on the PCI, the UE can determine the locations of theaforementioned DL-RS. The physical broadcast channel (PBCH), whichcarries a master information block (MIB), may be logically grouped withthe PSCH and SSCH to form a synchronization signal (SS)/PBCH block. TheMIB provides a number of RBs in the DL system bandwidth, a PHICHconfiguration, and a system frame number (SFN). The PDSCH carries userdata, broadcast system information not transmitted through the PBCH suchas system information blocks (SIBs), and paging messages.

As illustrated in FIG. 2C, some of the REs carry demodulation referencesignals (DM-RS) for channel estimation at the base station. The UE mayadditionally transmit sounding reference signals (SRS) in the lastsymbol of a subframe. The SRS may have a comb structure, and a UE maytransmit SRS on one of the combs. The SRS may be used by a base stationfor channel quality estimation to enable frequency-dependent schedulingon the UL. FIG. 2D illustrates an example of various channels within anUL subframe of a frame. A physical random access channel (PRACH) may bewithin one or more subframes within a frame based on the PRACHconfiguration. The PRACH may include six consecutive RB pairs within asubframe. The PRACH allows the UE to perform initial system access andachieve UL synchronization. A physical uplink control channel (PUCCH)may be located on edges of the UL system bandwidth. The PUCCH carriesuplink control information (UCI), such as scheduling requests, a channelquality indicator (CQI), a precoding matrix indicator (PMI), a rankindicator (RI), and HARQ ACK/NACK feedback. The PUSCH carries data, andmay additionally be used to carry a buffer status report (BSR), a powerheadroom report (PHR), and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with aUE 350 in an access network. In the DL, IP packets from the EPC 160 maybe provided to a controller/processor 375. The controller/processor 375implements layer 3 and layer 2 functionality. Layer 3 includes a radioresource control (RRC) layer, and layer 2 includes a packet dataconvergence protocol (PDCP) layer, a radio link control (RLC) layer, anda medium access control (MAC) layer. The controller/processor 375provides RRC layer functionality associated with broadcasting of systeminformation (e.g., MIB, Ms), RRC connection control (e.g., RRCconnection paging, RRC connection establishment, RRC connectionmodification, and RRC connection release), inter radio access technology(RAT) mobility, and measurement configuration for UE measurementreporting; PDCP layer functionality associated with headercompression/decompression, security (ciphering, deciphering, integrityprotection, integrity verification), and handover support functions; RLClayer functionality associated with the transfer of upper layer packetdata units (PDUs), error correction through ARQ, concatenation,segmentation, and reassembly of RLC service data units (SDUs),re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto transport blocks(TBs), demultiplexing of MAC SDUs from TBs, scheduling informationreporting, error correction through HARQ, priority handling, and logicalchannel prioritization. In an aspect, an RRC configuration may be usedby the UE to monitor for the GC-DCI.

The transmit (TX) processor 316 and the receive (RX) processor 370implement layer 1 functionality associated with various signalprocessing functions. Layer 1, which includes a physical (PHY) layer,may include error detection on the transport channels, forward errorcorrection (FEC) coding/decoding of the transport channels,interleaving, rate matching, mapping onto physical channels,modulation/demodulation of physical channels, and MIMO antennaprocessing. The TX processor 316 handles mapping to signalconstellations based on various modulation schemes (e.g., binaryphase-shift keying (BPSK), quadrature phase-shift keying (QPSK),M-phase-shift keying (M-PSK), M-quadrature amplitude modulation(M-QAM)). The coded and modulated symbols may then be split intoparallel streams. Each stream may then be mapped to an OFDM subcarrier,multiplexed with a reference signal (e.g., pilot) in the time and/orfrequency domain, and then combined together using an Inverse FastFourier Transform (IFFT) to produce a physical channel carrying a timedomain OFDM symbol stream. The OFDM stream is spatially precoded toproduce multiple spatial streams. Channel estimates from a channelestimator 374 may be used to determine the coding and modulation scheme,as well as for spatial processing. The channel estimate may be derivedfrom a reference signal and/or channel condition feedback transmitted bythe UE 350. Each spatial stream may then be provided to a differentantenna 320 via a separate transmitter 318TX. Each transmitter 318TX maymodulate an RF carrier with a respective spatial stream fortransmission.

At the UE 350, each receiver 354RX receives a signal through itsrespective antenna 352. Each receiver 354RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 356. The TX processor 368 and the RX processor 356implement layer 1 functionality associated with various signalprocessing functions. The RX processor 356 may perform spatialprocessing on the information to recover any spatial streams destinedfor the UE 350. If multiple spatial streams are destined for the UE 350,they may be combined by the RX processor 356 into a single OFDM symbolstream. The RX processor 356 then converts the OFDM symbol stream fromthe time-domain to the frequency domain using a Fast Fourier Transform(FFT). The frequency domain signal comprises a separate OFDM symbolstream for each subcarrier of the OFDM signal. The symbols on eachsubcarrier, and the reference signal, are recovered and demodulated bydetermining the most likely signal constellation points transmitted bythe base station 310. These soft decisions may be based on channelestimates computed by the channel estimator 358. The soft decisions arethen decoded and deinterleaved to recover the data and control signalsthat were originally transmitted by the base station 310 on the physicalchannel. The data and control signals are then provided to thecontroller/processor 359, which implements layer 3 and layer 2functionality.

The controller/processor 359 can be associated with a memory 360 thatstores program codes and data. The memory 360 may be referred to as acomputer-readable medium. In the UL, the controller/processor 359provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, and control signalprocessing to recover IP packets from the EPC 160. Thecontroller/processor 359 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DLtransmission by the base station 310, the controller/processor 359provides RRC layer functionality associated with system information(e.g., MIB, SIBs) acquisition, RRC connections, and measurementreporting; PDCP layer functionality associated with headercompression/decompression, and security (ciphering, deciphering,integrity protection, integrity verification); RLC layer functionalityassociated with the transfer of upper layer PDUs, error correctionthrough ARQ, concatenation, segmentation, and reassembly of RLC SDUs,re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; andMAC layer functionality associated with mapping between logical channelsand transport channels, multiplexing of MAC SDUs onto TBs,demultiplexing of MAC SDUs from TBs, scheduling information reporting,error correction through HARQ, priority handling, and logical channelprioritization.

Channel estimates derived by a channel estimator 358 from a referencesignal or feedback transmitted by the base station 310 may be used bythe TX processor 368 to select the appropriate coding and modulationschemes, and to facilitate spatial processing. The spatial streamsgenerated by the TX processor 368 may be provided to different antenna352 via separate transmitters 354TX. Each transmitter 354TX may modulatean RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a mannersimilar to that described in connection with the receiver function atthe UE 350. Each receiver 318RX receives a signal through its respectiveantenna 320. Each receiver 318RX recovers information modulated onto anRF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 thatstores program codes and data. The memory 376 may be referred to as acomputer-readable medium. In the UL, the controller/processor 375provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover IP packets from the UE 350. IP packets from thecontroller/processor 375 may be provided to the EPC 160. Thecontroller/processor 375 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

FIG. 4 is a diagram 400 illustrating a base station 402 in communicationwith a UE 404. Referring to FIG. 4, when the UE 404 turns on, the UE 404searches for a nearby NR network. The UE 404 discovers the base station402, which belongs to an NR network. The base station 402 transmits anSS block including the PSS, SSS, and the PBCH (including the MIB)periodically in different transmit directions 402 a-402 h. The UE 404receives the transmission 402 e including the PSS, SSS, and PBCH. Basedon the received SS block, the UE 404 synchronizes to the NR network andcamps on a cell associated with the base station 402.

In an aspect, a downlink indicator may be in DCI. For example, theindicator may be part of control information (e.g., DCI). Uplinkindicators may use a corresponding method or a corresponding method ofany of the systems and methods described herein.

A downlink indicator may be a post indication, e.g., appearing at thestart of a next slot. The post indication may indicate whether the URLCCdata is present or not at the slot before the indication.

In an aspect, a downlink indicator may be configured to be a widebandindication or a sub-band indication (e.g., up to 2 sub-bands)indication. Accordingly, in some aspects, the downlink indicator mayspread across a wide portion of a bandwidth. In other aspects, thedownlink indicator may be part of a sub-band.

Furthermore, a downlink indicator may be configured to indicate one ormore symbols by configuring the monitoring periodicity. For example, adownlink indicator may be configured to indicate one or more symbols ina mini-slot or an indicator may be sent every predetermined number ofmini-slots. Periodicity may be configured semi-statically ordynamically. Accordingly, in an aspect, periodicity may be configuredsemi-statically, e.g., the periodicity may be fairly fixed, but might beconfigurable when updated or some other period. In another aspect,periodicity may be configured dynamically, e.g., periodicity may beconfigured at any time or almost any time by a network to which a UE orbase station is attached.

FIG. 5 is a diagram illustrating an example of a DL frame structure 500.The DL frame structure 500 includes eMBB data 502 and URLLC data 506 ina PDSCH 504. DL frame structure 500 further includes PDCCH 510, anduplink short burst (ULSB) 512 portions. The URLLC data 506 and the eMBBdata 502 may be transmitted based on different transmission durations.For example, the eMBB data 502 may follow a long format (e.g., slotbased). The URLLC data 506 may follow a short format (e.g., mini-slotbased).

In a first radio access network (RAN1), dynamic resource sharing betweenURLLC data 506 and eMBB data 502 may be supported. Accordingly, theallocation of resources for the URLLC data 506 and the eMBB data 502 maybe changed dynamically. For example, the URLLC data 506 may preempt orpuncture a subset of resources occupied by on-going eMBB data 502. Whenthe URLLC data 506 preempts resources occupied by on-going eMBB data502, the URLLC data 506 may replace the overlapping resources occupiedby on-going eMBB data 502, e.g., the base station may transmit URLLCdata 506 instead of transmitting eMBB data 502 on the indicted PDSCH 504resources. When the URLLC data 506 punctures the resources occupied byon-going eMBB data 502 the URLLC data 506 may be transmitted at the sametime as the resources occupied by on-going eMBB data 502, e.g., the basestation may transmit the URLLC data 506 on PDSCH 504 resources allocatedfor the eMBB data 502.

In an aspect, for a downlink transmission, a URLLC may puncture eMBB.When a URLLC punctures an eMBB, the base station may only transmit theURLLC data in the resources occupied by the URLLC. The eMBB data may berate matched taking into account the missing resources. In other words,an eMBB UE may work around the resource elements that may be used forthe URLLC data. In such an example, a base station may be thetransmitter, and the UE the may be the receiver.

In an aspect, for an uplink transmission, an eMBB UE and a URLLC UE maytransmit simultaneously transmit using the same resources. Because theURLLC has very high performance requirement, the URLLC data is likely tobe transmitted with much higher power than the eMBB data in the occupiedresource. Accordingly, the URLLC data may puncture the eMBB data. In anaspect, when the eMBB UE and the URLLC UE are the same UE, the eMBB datatransmission may be skipped in the resources occupied by URLLC data. Foran eMBB UE receiving a downlink transmission, the resources used for aURLLC may be zeroed out and/or ignored. For an eMBB UE receiving a URLLCuplink transmission, the resources used for a URLLC may not be used bythe eMBB UE. Rather, the eMBB UE may rate match to use other availableresources that have been scheduled for the eMBB UE.

RAN1 may use a URLLC indication (e.g., URLLC indicator) to indicate whenthe URLLC data 506 preempts and/or punctures the eMBB data 502. Anindication of URLLC preemption or puncturing to an eMBB UE (104, 350,404) regarding an impacted eMBB resource may facilitate eMBB UE (104,350, 404) demodulation and decoding of a current transmission and/orsubsequent retransmissions.

FIGS. 6-11 illustrate examples of designs for an indication channel. Theexamples illustrate various locations within frame structures ofindication channel. In some examples, an indication channel may beseparate from eMBB data and frequency division multiplexed (FDM) or timedivision multiplexed (TDM). (See FIGS. 6-8, 10, and 11.) In someexamples, an indication channel may be embedded in eMBB data. (See FIGS.9 and 11.) In other examples, an indication channel may be signaled inthe grant or Radio Resource Control (RRC) configured per UE or pernetwork configuration. (See FIGS. 6-8, 10, and 11.)

FIG. 6 is a diagram illustrating an example of a DL frame structure. TheDL frame structure 600 includes eMBB data 602, a PDSCH 604, URLLC data606, URLLC indicators 608, a PDCCH 610, uplink short burst (ULSB) 612.

FIG. 6 illustrates an example of a separate indication channel design.In some examples of indication channel signaling, an indication may besignaled per mini-slot or per a plurality of mini-slots. For example,one or more of the URLLC indicators 608 may be used.

In an aspect, the indication may be wideband based, i.e., the indicationmay indicate that the preemption or puncture will be of, for example, anentire available band. For example, referring to FIG. 2B, the one ormore URLLC indicators 608 may indicate whether URLLC datapreempts/punctures the entire DL system bandwidth. In an aspect, theindication may be sub-band based, i.e., the indication may indicate thatthe preemption or puncture will use less than the entire available band,e.g., a sub-band. For example, referring to FIG. 2B, the one or moreURLLC indicators 608 may indicate whether URLLC data preempts/puncturesa particular subset of subcarriers of the entire DL system bandwidth. Insome aspects, the indication may be RB based or UE specific. Wide bandor sub-band based indications may apply to all UEs using a wideband orthat sub-band, e.g., for preempting or puncturing with URLLC.

A positive indication of a URLLC data 606 transmission, e.g., during ascheduled eMBB data 602 transmission, may impact all RBs in a set of RBsin the PDSCH data even though not all RBs in the set of RBs are used byURLLC data 606 transmission. Accordingly, the impact on all the RBs maybe a waste of resources and a performance degradation. In some examples,the data in the set of RBs may be incomplete due to the PDSCH data. Inanother example, it may be possible to re-generate the data from theeMBB data 602, e.g., punctured by the PDSCH data, for example, due todata redundancy.

In an example, the indication may be RB based. Thus, the indication maybe made on a per RB basis or a per RB group basis, e.g., every 4 RBs.For example, referring to FIGS. 2A, 2B, the one or more URLLC indicators208 may providing an indication for x RBs, where x≥1.

In a UE specific example, an indication may be sent on a per UE basis.Accordingly, such indication may be sent directly to a particular UE,and may apply just for that UE. In an aspect, an indication may havedifferent indication periodicity. Accordingly, the indicationperiodicity may be settable. For example, URLLC indicator periodicitymay be configured semi-statically or dynamically. For a UE specificindication, the indicator may be per mini-slot or per mini-slot group.Some examples may use a single bit indication per UE or multiple bitsper UE for the indication. In the single bit indication case, the bitmay be set when at least one RB of the eMBB UE is occupied. Anindication with multiple bits may provide better frequency resolution toindicate which RB or RB groups of an eMBB UE are occupied.

An example URLLC indicator may use a UL long burst structure at a slotlevel in terms of DMRS design, or other design features. For example, aPUCCH channel structure may be used for transmitting the URLLCindicator.

Shared DMRS may be used for all indications across all the mini-slots.Indication bits may be separately encoded or jointly encoded. Jointencoding may have better performance but may delay decoding.Additionally, joint encoding may need to buffer PDSCH. Separate encodingmay support instantaneous decoding of indication bits, but bits may besplit into groups of indication bits. A URLLC indicator may betransmitted using TDM/FDM or CDM.

FIG. 7 is a diagram illustrating an example of a DL frame structure. TheDL frame structure having a separate indication channel design 700includes eMBB data 602, a PDSCH 604, URLLC data 606, a URLLC indicator608, a PDCCH 610, uplink short burst (ULSB) 612. The example illustratesa separate indication channel design 700. The separate indicationchannel design 700 may use an UL short burst structure at mini-slotlevel. The separate indication channel design 700 may have short burstwith or without DMRS (e.g., to achieve DMRS sharing between differentmini-slots). Additionally, the separate indication channel design 700may support instantaneous decoding of indication bits. As illustrated inFIG. 7, the URLLC indicator 608 may be part of the PDSCH 604.

FIG. 8 is a diagram illustrating an example of a DL frame structure. TheDL frame structure 800 includes eMBB data 602, a PDSCH 604, URLLC data606, a URLLC indicator 608 (608A, 608B), a PDCCH 610, uplink short burst(ULSB) 612. The URLLC indicator 608A is a group common PDCCH in thePDSCH 604. The URLLC indicator 608A is a group common PDCCH in the PDCCH610. The example may use a group common PDCCH 610 structure (PCFICH-typechannel), i.e., DCI. The indicator may be conveyed in a group-common DCImessage. For example, a group common PDCCH 610 may be used by a commongroup of devices. In one example, a BS may send to a set of UEs DCImessage including one or more URLLC indicators every mini-slot. Inanother example, a common PDCCH 610 may be used by a common group ofdevices every mini-slot. In one example, a BS may send to a set of UEsDCI message including one or more URLLC indicators every few mini-slots.How often DCI messages are sent is configurable. In an example, the RSmay be shared with DCI per slot. In another example, the URLLC indicatormay use DCI message once per slot. When the URLLC indicator uses DCImessage once per slot, that indicator may be transmitted in thebeginning of the next slot after URLLC data is transmitted.

FIG. 9 is a diagram illustrating an example of a DL frame structure. TheDL frame structure 600 includes eMBB data 602, a PDSCH 604, URLLC data606, a URLLC indicator 608, a PDCCH 610, uplink short burst (ULSB) 612.

An example may use an embedded indication channel (URLLC indicator 608)design. The embedded indication channel design may be embedded in theeMBB data 602 region. Additionally, the indication channel may have acomb based structure, as illustrated in FIG. 9.

In an example, every four tones may be used for an indication channel.Additionally, in an example, when a URLLC data 606 transmission is notpresent, the URLLC indicator 608 might not be sent, e.g., to saveoverhead. Additionally, in an example, when a URLLC data 606transmission is present, the comb based indication channel may also beturned into DMRS for the corresponding URLLC UE 104, 350, 404. In anaspect, the URLLC data 606 may rate match around the indication channel(DMRS).

For an indication monitoring duration (one or more mini-slot(s)), theeMBB UE may perform a blind detection of locations for URLLC DMRS to seeif the URLLC data 606 is present. The blind detection may be similar toan ACK on the PUSCH in LTE but in a comb based transmission. RB bundling(e.g., sub-band bundling) of an indication channel may be used toincrease processing gain and to ensure blindly decoding reliability.Additionally, spatial separation, scrambling, precoding, or otherwireless communication processes may be used to reduce a false alarmrate in blind decoding.

An aspect may include a cell-specific collection of RBs that may be usedby a UE that transmits a URLLC. The UE that transmits a URLLC may besignaled by a broadcast messages (or in a grant). The UE that transmitsa URLLC may then use predefined mini-slots within the RBs to transmit aURLLC indicator. The URLLC indicator may points to the mini-slots whichare being utilized. Additionally, the mini-slots being utilized may bejointly or separately encoded depending on requirements for granularityof the information in the mini-slots versus overhead for processing themini-slots.

The following aspects may also hold for the indicator design regardlesswhether the indicator is transmitted in separate resource from the eMBBdata or embedded in the URLLC.

In an aspect, an indication design may include an indication that may beat the beginning or end of a mini-slot. In another example, theindication may be at the beginning or end of a slot. In yet anotherexample, the indication may be at the beginning or end of a set ofmultiple-mini-slots.

In an aspect, an indication design may be per mini-slot(s). A permini-slot design may enable pipeline demodulation and/or decodeprocessing.

In an aspect, an indication design may include the indication may besignaled dynamically or semistatically, whether indication is separateor embedded, whether indication is sub-band or per UE can be signaled,and/or granularity of indication.

In an aspect, an indication may be broadcast and may be sub-band based,such as an indication of preemption applying to a correspondingsub-band.

In an aspect, an indication may be unicast to a UE 104, 350, 404. Theindication may be per UE per mini-slot (per preemption unit).Additionally, multiplexing across UEs may be TDM/FDM or CDM.Additionally, encoding of the indicator channel may be independently orgroup encoded.

FIG. 10 is a diagram illustrating an example of a UL frame structure.The DL frame structure 1000 includes eMBB data 1002, a PDSCH 1004, URLLCdata 1006, a URLLC indicator 1008, a PDCCH 1010, uplink short burst(ULSB) 1012. The ideas discussed with respect to FIGS. 6-9 for DLtransmissions from a base station 102, 310, 402 to a UE 104, 350, 404may be applied to UL transmissions from a UE 104, 350, 404 to a basestation 102, 310, 402.

For scheduled URLLC data 1006, the base station 102, 310, 402 may needto send a URLLC indicator 608 to the eMBB UE beforehand so that the eMBBPDSCH 1004 may rate match around URLLC data 1006.

Some examples may use the same indication structure described withrespect to previous FIGS. 6-9 to indicate a URLLC data 1006 transmissionin an UL slot. For example, as discussed above, FIG. 6 is a diagramillustrating an example of a DL frame structure. The DL frame structure600 of FIG. 6 includes eMBB data 602, a PDSCH 604, URLLC data 606, URLLCindicators 608, a PDCCH 610, uplink short burst (ULSB) 612. FIG. 6illustrates an example of a separate indication channel design. In someexamples of indication channel signaling, an indication may be signaledper mini-slot or per a plurality of mini-slots. For example, one or moreof the URLLC indicators 608 may be used. FIG. 7 is a diagramillustrating an example of a DL frame structure. The DL frame structureof the indication channel design 700 includes eMBB data 602, a PDSCH604, URLLC data 606, a URLLC indicator 608, a PDCCH 610, ULSB 612. Theexample illustrates a separate indication channel design 700. FIG. 8 isa diagram illustrating an example of a DL frame structure. The DL framestructure 800 includes eMBB data 602, a PDSCH 604, URLLC data 606, aURLLC indicator 608, a PDCCH 610, ULSB 612. FIG. 9 is a diagramillustrating an example of a DL frame structure. The DL frame structure600 includes eMBB data 602, a PDSCH 604, URLLC data 606, a URLLCindicator 608, a PDCCH 610, ULSB 612.

In some examples, the URLLC indicator 1008 may be transmitted in aprevious slot with a separate channel. Some examples may reuse UL longand/or short burst channel structure in a main DL portion. Some examplesmay reuse DCI in either main DL portion or in PDCCH region. Someexamples may transmit in a current slot in PDCCH region. Some examplesmay reuse DCI. The indication channel for DL and UL URLLC data 1006transmission may be TDM/FDM/CDM.

As illustrated in FIG. 10, the URLLC indicator 1008 may be transmittedembedded 1114, in a previous slot 1014 or in a current slot 1016.

FIG. 11 is a diagram illustrating an example of a UL frame structure.The DL frame structure 1100 includes eMBB data 1102, a PUSCH 1104, URLLCdata 11011, a URLLC indicator 1108, a PDCCH 1110, uplink short burst(ULSB) 1112.

FIG. 11 illustrates examples of URLLC indications 1108 for transmissionwithout scheduling. The URLLC scheduling request (SR) or URLLC data 1106may puncture eMBB PUSCH 1104. In the example of FIG. 11, the URLLC UE104, 350, 404 may need to transmit an indication to the base station102, 310, 402 (e.g., eNB, gNB). The eMBB UE 104, 350, 404 may not beaware of the presence of URLLC transmission. Accordingly, an indicationmay be transmitted in separate channel in a long burst, or in a shortburst. In an example, an indication may be a short transmission.Additionally, in some examples, the URLLC indicator 1108 from differentURLLC UEs 104, 350, 404 may be TDM/FDM/CDM.

In some examples, the URLLC indicator 1108 may be embedded in long burstwith a comb based structure. As illustrated in FIG. 11, the URLLCindicator 1108 may be transmitted embedded 1114, in a ULSB 1112 in ashort burst, and/or in the PUSCH 1104 in a long burst.

As described herein, in an aspect, a URLCC device may send an indicatorof URLLC data. The indicator of the URLLC data may, in some examples, besent regardless of whether URLLC data is present or not. For example,the URLLC indicator may indicate that URLLC data is present and wherethe URLLC data is located in a transmission. The URLLC indicator mayalso indicate that no URLLC data is present in a particulartransmission. Thus, a URLLC device may transmit a URLLC indicator toanother device, such as an eMBB UE. The other device may be required tomonitor for the URLLC indicator to determine if URLCC data is presentand to then take appropriate action when the URLLC data is present. Forexample, an eMBB UE may rate match around the URLLC data or zero out anyreceived URLLC data base on the existence of URLLC data as may beindicated by the URLCC indicator. In a case when the URLCC indicatorindicates that no URLLC data, the other device may do nothing. Forexample, the eMBB UE will not be required to rate match any transmitteddata around URLCC data or zero out any received data. In other examples,URLLC indicators might be sent only when URLLC data is present.

FIG. 12 is a flowchart 1200 of a method of wireless communication. Themethod may be performed by a base station (e.g., the base station 102,310, 402, the apparatus 1802, 1802′). At 1202, the base stationgenerates a set of resource blocks including at least one of eMBB dataor URLLC data in a PDSCH. The URLLC data may be one of embedded in theeMBB data or unembedded in the eMBB data. For example, referring toFIGS. 6-9, the base station (e.g., base station 102, 310, 402, theapparatus 2202, 2202′) may generate a set of resource blocks such as theresource blocks illustrated in FIGS. 2A, 2C. The resource blocks mayinclude at least one of eMBB data 602 or URLLC data 606 in a PDSCH 604.An example PDSCH 604 structure is illustrated in FIG. 2B. As illustratedin FIGS. 6-9, the URLLC data 606 may be embedded in the eMBB data 602.The URLLC data 606 may be unembedded, or separated from, the eMBB data602. For example, there may be no URLLC data 606. Generating a set ofresource blocks including at least one of eMBB data 602 or URLLC data ina PDSCH may include obtaining MBB data, the URLLC data, or both MBB dataand the URLLC data, and mapping the data to the set of resource blocks.Generating a set of resource blocks including at least one of eMBB data602 or URLLC data in a PDSCH may include embedding the URLLC data in theeMBB data 602 or not embedding the URLLC data in the eMBB data 602.

At 1204, the base station generates a URLLC indicator indicating whetherthe set of resource blocks includes at least part of the URLLC data. Forexample, as illustrated in FIGS. 6-9, the base station (e.g., basestation 102, 310, 402, the apparatus 2202, 2202′) generates a URLLCindicator 608 indicating whether the set of resource blocks includes theURLLC data 606. In an aspect, the URLLC indicator 608 may be a downlinkindicator in DCI. For example, FIG. 8, illustrates a group common PDCCHindicator 608B, i.e., a downlink indicator in DCI. Generating a URLLCindicator 608 indicating whether the set of resource blocks includes theURLLC data 606 may include determining when the set of resource blocksis to includes the URLLC data 606 and creating an indicator 608 based onthat determination.

In an aspect, an indication may include a post indication. For example,the indication in FIG. 8 may be a post indication, i.e., an indicationat the start of the next one or more slots. For example, post indicationmay appear at the start of the next slot. See, for example, FIG. 8, inwhich the group common PDCCH indicator 608B is in a slot aftercorresponding URLLC preempt or puncturing resources occupied by anongoing eMBB communication has occurred. The indication may indicatewhether the URLLC data 606 is present or not. In an aspect, anindication may be configured to be a wideband indication, e.g., the dataspace preempted (which may or may not be completely used for data) usesall or a large portion of a band or bands in a slot. For example,preemption may extend across all subcarriers of a carrier. FIG. 2Billustrates an example downlink system bandwidth where preemption mayoccur. In an aspect, an indication may be configured to be a sub-bandindication, e.g., the data space preempted—which may or may not becompletely used for data) uses a small or smaller portion of a band orbands in a slot as compared to wideband. For example, preemption mayextend across one or more subsets of the subcarriers of the carrier.FIG. 2B illustrates an example downlink system bandwidth wherepreemption may occur. The sub-band indication may be used to indicateuse of two sub-bands. The indication may be configured to indicate oneor more symbols by configuring the monitoring periodicity.

The generation of a URLLC indicator 608 indicating that the URLLC data606 is within the portion of the resource blocks with the eMBB data 602may include determining that the URLLC data 606 is within the portion ofthe resource blocks with the eMBB data 602 and/or creating the URLLCindicator 608 based on the determination.

At 1206, the base station sends, to at least one UE, the URLLC indicatorand the set of resource blocks including the at least one of the eMBBdata or the URLLC data. The URLLC indicator may be sent separate fromthe URLLC data within DCI of a PDCCH. For example, referring to FIGS.6-9, the base station (e.g., base station 102, 310, 402, the apparatus2202, 2202′) may send, to at least one UE (e.g., UE 104, 350, 404, theapparatus 2002, 2002′) the URLLC indicator 608 and the set of resourceblocks including the at least one of the eMBB data 602 or the URLLC data606. Referring to FIGS. 6-8, the URLLC indicator 608 may be sentseparate from the URLLC data 606 within DCI of a PDCCH 610. For example,see the group common PDCCH indicator 608B of FIG. 8. An example PDCCH isillustrated in FIG. 2B. In some aspects, an indicator 608 may be sentregardless of the presence of URLLC data 606. For example, a URLLCindicator 608 may be sent periodically. In other aspects, a URLLCindicator 608 may be sent only when URLLC data 606 is present. Sendingthe URLLC indicator 608 and the set of resource blocks including theeMBB data 602 and the URLLC data 606 to at least one UE (e.g., UE 104,350, 404, the apparatus 2002, 2002′) may include providing the URLLCindicator 608 and the set of resource blocks to a transmit device and/orcausing the URLLC indicator 608 and the set of resource blocks to betransmitted. Sending, to at least one UE (e.g., UE 104, 350, 404, theapparatus 2002, 2002′) the URLLC indicator 608 and the set of resourceblocks including the at least one of the eMBB data 602 or the URLLC data606 may include transferring information to a transmitter and causingthe transmitter to transmit the information. The information may includethe URLLC indicator 608 and the set of resource blocks including the atleast one of the eMBB data 602 or the URLLC data 606. The informationmay also indicate how to send the URLLC indicator 608 and the set ofresource blocks, e.g., the URLLC indicator 608 may be sent embeddedwithin the URLLC data 606 or may be sent separate from the URLLC data606 within DCI of a PDCCH (indicator 608B). The URLLC indicator 608 maybe within a separate indicator channel.

At 1208, the base station configures a periodicity for sending the URLLCindicator. For example, the base station (e.g., base station 102, 310,402, the apparatus 2202, 2202′) may configure a periodicity for sendingthe URLLC indicator 608. Thus, the timing for sending of the URLLCindicator may be settable. The timing for the periodicity may bedetermined by the base station (e.g., base station 102, 310, 402, theapparatus 2202, 2202′) and the base station (e.g., base station 102,310, 402, the apparatus 2202, 2202′) may transmit that timing to a UE(e.g., UE 104, 350, 404, the apparatus 2002, 2002′), e.g., as RRCsignaling. The base station (e.g., base station 102, 310, 402, theapparatus 2202, 2202′) may dynamically configure a periodicity forsending the URLLC indicator 608. Accordingly, the indicator may be sentwith a changeable periodicity. In another aspect, the base station(e.g., base station 102, 310, 402, the apparatus 2202, 2202′) maysemi-statically configure a periodicity for sending the URLLC indicator.Accordingly, the indicator may be sent with a periodicity that does notchange or does not change often, e.g., such as when communicationsbetween particular UE and a particular base station begins. Configuringa periodicity for sending the URLLC indicator 608 may include ofselecting a time period and/or applying the time period to the sendingof step 1206.

In an aspect, the URLLC indicator may be sent separately from the URLLCdata. The URLLC indicator may be within the DCI of a group-common PDCCH.For example, the URLLC indicator 608 may be sent separately from theURLLC data 606. (See FIGS. 7-8.) The URLLC indicator 608 may be withinthe DCI of a group-common PDCCH 610. (See 608B, FIG. 8.)

In an aspect, the set of resource blocks from the base station includesthe eMBB data. The indicator indicates whether the URLLC data isembedded within the eMBB data. For example, referring to FIGS. 6-9, inan aspect, the set of resource blocks (e.g., see RB, FIGS. 2A, 2C) fromthe base station (e.g., base station 102, 310, 402, the apparatus 2202,2202′) includes the eMBB data 602. Additionally, the indicator 608indicates whether the URLLC data 606 is embedded within the eMBB data602.

In an aspect, the set of resource blocks from the base station includesthe URLLC data in the PDSCH. Additionally, the URLLC indicator indicatesthat the URLLC data is present in the set of resource blocks. Forexample, referring to FIGS. 6-9, the set of resource blocks from thebase station (e.g., base station 102, 310, 402, the apparatus 2202,2202′) includes the URLLC data 606 in the PDSCH 604. Additionally, theURLLC indicator 608 indicates that the URLLC data 606 is present in theset of resource blocks. (Examples of reference blocks may be found inFIGS. 2A, 2C.

In an aspect, the URLLC indicator is sent embedded within the URLLCdata. For example, referring to FIGS. 6-9, in an aspect, the URLLCindicator 608 may be sent embedded within the URLLC data 606.

In an aspect, the set of resource blocks is sent in a slot before a slotin which the URLLC indicator is sent. The URLLC indicator may be a postindication indicating whether the set of resource blocks includes atleast part of the URLLC data. For example, the set of resource blocks issent in the slot before the slot in which the URLLC indicator 608 issent. The URLLC indicator 608 may be a post indication indicatingwhether the set of resource blocks includes the URLLC data 606. Forexample, the URLLC data 606 before is illustrated as being before URLLCindicator 608B in FIG. 8.

FIG. 2B illustrates examples of downlink system bandwidth. In an aspect,the URLLC indicator is wideband based and indicates that the URLLC dataextends across all subcarriers of a carrier. In an aspect, the URLLCindicator is subband based and indicates that the URLLC data extendsacross one or more subsets of the subcarriers of the carrier. Forexample, the URLLC indicator 608 may be wideband based and may indicatethat the URLLC data 606 extends across all subcarriers of a carrier. Inan aspect, the URLLC indicator 608 is subband based and indicates thatthe URLLC data 606 extends across one or more subsets of the subcarriersof the carrier.

In an aspect, the set of resource blocks may be transmitted in a slotbefore a slot in which the URLLC indicator is received. The URLLCindicator may include a post indication. The post indicating mayindicate whether the set of resource blocks received in the slot beforethe slot in which the URLLC indicator is transmitted includes the URLLCdata.

An aspect may transmit a configuration for transmitting the URLLCindicator. The configuration may specify a periodicity at which theURLLC indicator is transmitted.

FIG. 13 is a flowchart 1300 of a method of wireless communication. Themethod may be performed by a UE (e.g., the UE 104, 350, 404, theapparatus 2002, 2002′). At 1302, the UE receives a set of resourceblocks from a base station including eMBB data. For example, referringto FIGS. 6-9, the UE (e.g., UE 104, 350, 404, the apparatus 2002, 2002′)may receive a set of resource blocks from a base station (e.g., basestation 102, 310, 402, the apparatus 2202, 2202′) including eMBB data602. The receiving the set of resource blocks including a PDSCH from thebase station may include tuning to a base station, receiving data fromthe base station, determining the resource blocks from the base station,and/or determining the PDSCH from the received resource block.

At 1304, the UE receives a URLLC indicator from the base station. TheURLLC indicator is received within DCI of a PDCCH. The URLLC indicatorindicates whether the set of resource blocks includes the URLLC data.The URLLC data may be embedded in eMBB data. For example, the UE (e.g.,UE 104, 350, 404, the apparatus 2002, 2002′) may receive a URLLCindicator 608 from the base station (e.g., base station 102, 310, 402,the apparatus 2202, 2202′). For example, referring to FIG. 9, the URLLCindicator 608 may also be received embedded within the URLLC data 606.For specifically, referring to FIG. 8, the URLLC indicator 608 may bewithin DCI of a PDCCH 610. For example, see the group common PDCCHindicator 608B of FIG. 8. An example format for the PDCCH may be foundin FIG. 2B. The URLLC indicator 608 may be received URLLC indicator 608may be sent as part of the bits that make up the DCI. The URLLCindicator 608 indicates whether the set of resource blocks include theURLLC data 606. Referring to FIGS. 6-9, in an example, the URLLC data606 may be embedded in eMBB data 602. The URLLC data 606 does not alwayspreempt or puncture resources occupied eMBB communication. In someaspects, an indicator may be received regardless of the presence ofURLLC data 606. For example, a URLLC indicator may be receivedperiodically. In other aspects, a URLLC indicator may be received onlywhen URLLC data 606 is present. Receiving a URLLC indicator 608 from thebase station may include tuning to a base station, receiving data fromthe base station, and/or determining the indicator from the basestation.

At 1306, the UE determines, based on the URLLC indicator, whether theset of resource blocks includes the URLLC data embedded within the eMBBdata. For example, referring to FIGS. 6-9, the UE (e.g., UE 104, 350,404, the apparatus 2002, 2002′) determines, based on the URLLC indicator608, whether the set of resource blocks includes the URLLC data 606embedded within the eMBB data 602. Determining, based on the URLLCindicator, whether the set of resource blocks includes the URLLC data606 may include processing received signals including the URLLCindicator to determine the URLLC indicator and processing the URLLCindicator to determine whether the set of resource blocks includes theURLLC data 606.

At 1308, a decision is made based on the determination at 1306. When theURLLC indicator determines that the set of resource blocks includes theURLLC data block 1310 may be executed. When the URLLC indicatordetermines that the set of resource blocks does not include the URLLCdata block 1312 may be executed.

At 1310, the UE processes the set of resource blocks based on a resultof determining whether the set of resource blocks includes the URLLCdata (e.g., when eMBB data is present in the set of resource blocks,take into account when processing the eMBB data that the URLLC data isembedded within the eMBB data). For example, the UE (e.g., UE 104, 350,404, the apparatus 2002, 2002′) may process the set of resource blocksbased on a result of determining whether the set of resource blocksincludes the URLLC data 606 using one or more of the processors 356,368, 359 illustrated in FIG. 3. The received set of resource blocksincluding the at least one of the eMBB data 602 or the URLLC data 606.Processing the received set of resource blocks including the at leastone of the eMBB data 602 or the URLLC data 606 may include reading amemory location storing the URLLC indicator to determine the indicator'sstate (or otherwise determining the indicator's state) and processingthe resource blocks base on the indicator's state. In an aspect,processing may include either rate matching around the embedded URLLCdata or discarding the URLLC data based on the URLLC indicator. In anaspect, the UE may send an ACK/NACK as part of 1310.

At 1312, the UE processes the set of resource blocks based on a resultof determining whether the set of resource blocks includes the URLLCdata (e.g., when no URLLC data is present). For example, the UE (e.g.,UE 104, 350, 404, the apparatus 2002, 2002′) may process (e.g., in aprocessor 356, 368, 359), process the set of resource blocks based on aresult of determining whether the set of resource blocks includes theURLLC data 606. Processing the received set of resource blocks includingthe at least one of the eMBB data 602 or the URLLC data 606 may includereading a memory location storing the URLLC indicator to determine theindicator's state (or otherwise determining the indicator's state) andprocessing the resource blocks base on the indicator's state. In anaspect, the UE may send an ACK/NACK as part of 1312.

At 1314, a UE receives a configuration for receiving the URLLC indicatorat a particular periodicity. The configuration may be receiveddynamically or semi-statically. For example, a UE (e.g., UE 104, 350,404, the apparatus 2002, 2002′) may receive a configuration for sendingthe URLLC indicator at a particular periodicity. In an aspect, the UE(e.g., UE 104, 350, 404, the apparatus 2002, 2002′) may dynamicallyreceive a configuration for sending the URLLC indicator 608 at aparticular periodicity. Accordingly, the indicator may be sent with achangeable periodicity. In an aspect, the UE (e.g., UE 104, 350, 404,the apparatus 2002, 2002′) may semi-statically receive a configurationfor sending the URLLC indicator 608 at a particular periodicity.Accordingly, the indicator may be sent with a periodicity that does notchange or does not change often, e.g., such as when communicationsbetween particular UE and a particular base station begins. In anaspect, the configuration may specified a periodicity at which the URLLCindicator is transmitted. In an aspect, after preemption has occurred, aUE (e.g., UE 104, 350, 404, the apparatus 2002, 2002′) may send anacknowledge (ACK) when some preempted data has decoded properly at theUE, e.g., because of replacement, redundancy, or both; or a negativeacknowledge (NACK) when some preempted data has decoded improperly. Forexample, the ACK or NACK may be sent back to the base station. An aspectmay transmit one of an ACK or a NACK based on whether the set ofresource blocks are properly decoded when processing the set of resourceblocks. The block 1314 may occur to prepare for a subsequent executionof the flowchart (or as an initial step in the flow chart) in someexamples,

In an aspect, the URLLC indicator may be received separately from theURLLC data. The URLLC indicator may be within the DCI of a group-commonPDCCH. For example, referring to FIGS. 7-8, the URLLC indicator 608 maybe received separately from the URLLC data 606. The URLLC indicator 608may be within the DCI of a group-common PDCCH 610. For example, FIG. 8,URLLC indicator 608B illustrates a URLLC indicator 608 within the DCI ofa group-common PDCCH 610.

In an aspect, the set of resource blocks from the base station includesthe eMBB data. The indicator indicates whether the URLLC data isembedded within the eMBB data. For example, referring to FIGS. 6-9, inan aspect, the set of resource blocks (from the base station (e.g., basestation 102, 310, 402, the apparatus 2202, 2202′) includes the eMBB data602. The indicator 608 indicates whether the URLLC data 606 is embeddedwithin the eMBB data 602.

In an aspect, the set of resource blocks from the base station includesthe URLLC data in the PDSCH. Additionally, the URLLC indicator indicatesthat the URLLC data is present in the set of resource blocks. Forexample, referring to FIGS. 6-9, the set of resource blocks from thebase station (e.g., base station 102, 310, 402, the apparatus 2202,2202′) includes the URLLC data 606 in the PDSCH 604. Additionally, theURLLC indicator 608 indicates that the URLLC data 606 is present in theset of resource blocks.

In an aspect, the URLLC indicator is received embedded within the URLLCdata. For example, referring to FIGS. 6-9, in an aspect, the URLLCindicator 608 may be received embedded within the URLLC data 606.

In an aspect, the set of resource blocks is received in a slot before aslot in which the URLLC indicator is received. The URLLC indicator maybe a post indication indicating whether the set of resource blocksincludes the URLLC data. For example, the set of resource blocks isreceived in a slot before the slot in which the URLLC indicator 608 isreceived. The URLLC indicator 608 may be a post indication indicatingwhether the set of resource blocks includes the URLLC data 606. Forexample, see the URLLC data 606, which is before the URLLC indicator608B in FIG. 8.

In an aspect, the URLLC indicator is wideband based and indicates thatthe URLLC data extends across all subcarriers of a carrier. In anaspect, the URLLC indicator is subband based and indicates that theURLLC data extends across one or more subsets of the subcarriers of thecarrier. For example, the URLLC indicator 608 may be wideband based andmay indicate that the URLLC data 606 extends across all subcarriers of acarrier. In an aspect, the URLLC indicator 608 is subband based andindicates that the URLLC data 606 extends across one or more subsets ofthe subcarriers of the carrier.

In an aspect, the set of resource blocks may be received in a slotbefore a slot in which the URLLC indicator is received. The URLLCindicator may include a post indication. The post indicating mayindicate whether the set of resource blocks received in the slot beforethe slot in which the URLLC indicator is received includes the URLLCdata.

An aspect may receive a configuration for receiving the URLLC indicator.The configuration may specify a periodicity at which the URLLC indicatoris received.

FIG. 14 is a flowchart 1400 of a method of wireless communication. Themethod may be performed by a UE (e.g., the UE 104, 350, 404, theapparatus 2002, 2002′). At 1402, a UE generates a set of resource blocksincluding URLLC data. For example, a UE 104, 350, 404 may generate a setof resource blocks including URLLC data 1106. (See FIG. 11.)

At 1404, a UE generates a URLLC indicator indicating that the URLLC datais in a subset of the set of resource blocks and is within the PUSCH.For example, the UE may generate a URLLC indicator 1108 indicating thatthe URLLC data 1106 is in a subset of the set of resource blocks and iswithin the PUSCH 1116. (See FIG. 11.)

At 1406, a UE sends, to a base station, the URLLC indicator and the setof resource blocks including the URLLC data. For example, the UE 104,350, 404 sends, to a base station 102, 310, 402, the URLLC indicator1108 and the set of resource blocks including the URLLC data 1106. (SeeFIG. 11.) In some aspects, an indicator may be sent regardless of thepresence of URLLC data. For example, a URLLC indicator may be sentperiodically. In other aspects, a URLLC indicator may be sent only whenURLLC data is present.

At 1408, a UE receives a configuration for sending the URLLC indicatorat a particular periodicity, wherein the configuration is received oneof dynamically or semi-statically. For example, a UE 104, 350, 404receives a configuration for sending the URLLC indicator 1108 at aparticular periodicity, wherein the configuration is received one ofdynamically or semi-statically.

In an aspect, the URLLC indicator 1108 may be frequency divisionmultiplexed, time division multiplexed, and/or code division multiplexedinto a subset of the set of resource blocks separate from the eMBB data1102 (1116), or embedded in the URLLC data 1106 within the subset of theset of resource blocks (1114).

In an aspect, the URLLC indicator 1108 does not overlap with the eMBBdata 1102 (1116).

In an aspect, the URLLC indicator 1108 may be sent in a URLLC indicatorchannel with DMRS (in resource blocks 1114). In an aspect, a wirelesscommunication device may check to determine whether certain tonescontain a DMRS pattern. Certain tones containing a DMRS pattern mayindicate that the URLLC data is present. In an aspect, the URLLC datapunctures eMBB data in the PDSCH.

In an aspect, the URLLC indicator 1108 may be embedded in the URLLC data1106 (1114).

In an aspect, the URLLC indicator 1108 and the URLLC data 1106 may havea comb subcarrier structure (e.g., in resource blocks 1114).

In an aspect, the URLLC indicator 1108 may be sent in a URLLC indicatorchannel with DMRS (e.g., in resource blocks 1114). In an aspect, awireless communication device may check to determine whether certaintones contain a DMRS pattern. Certain tones containing a DMRS patternmay indicate that the URLLC data is present. In an aspect, the URLLCdata punctures eMBB data in the PDSCH.

In an aspect, the URLLC indicator includes a post indication.

In an aspect, the URLLC indicator further indicates that the URLLC datais preempting one of wideband data or sub-band data.

FIG. 15 is a flowchart 1500 of a method of wireless communication. Themethod may be performed by a base station (e.g., the base station 102,310, 402, the apparatus 1802, 1802′). At 1502, the base station receivesa set of resource blocks from a UE. For example, the base station 102,310, 402 receives a set of resource blocks from a UE 104, 350, 404.

At 1504, the base station (e.g., 102, 310, 402, 1802, 1802′) receives aURLLC indicator from the UE (e.g., UE 104, 350, 404, the apparatus 2002,2002′). In some aspects, an indicator may be received regardless of thepresence of URLLC data. For example, a URLLC indicator may be receivedperiodically. In other aspects, a URLLC indicator may be received onlywhen URLLC data is present.

At 1506, the base station determines, based on the URLLC indicator, thata subset of the set of resource blocks includes URLLC data. For example,the base station 102, 310, 402, 1802, 1802′ may determine, based on theURLLC indicator 1108, that a subset of the set of resource blocksincludes URLLC data 1106.

In an aspect, the URLLC indicator 1108 may be frequency divisionmultiplexed, time division multiplexed, code division multiplexed into asubset of the set of resource blocks separate from the eMBB data 1102(1116), and/or embedded in the URLLC data 1106 within the subset of theset of resource blocks (1114).

In an aspect, the URLLC indicator 1108 may identify a location of theURLLC data 1106.

In an aspect, the URLLC indicator 1108 may be frequency divisionmultiplexed with a PDCCH 1110 in the subset of the set of resourceblocks and/or frequency division multiplexed with a PUSCH 1104 in thesubset of the set of resource blocks. (See FIG. 11.)

In an aspect, the URLLC indicator 1108 may be embedded in the URLLC data1106. (See FIG. 11.)

In an aspect, the URLLC indicator 1108 and the URLLC data 1106 may havea comb subcarrier structure (e.g., in resource blocks 1114).

In an aspect, the URLLC indicator 1108 may be sent in a URLLC indicatorchannel with DMRS (e.g., in resource blocks 1114). In an aspect, awireless communication device may check to determine whether certaintones contain a DMRS pattern. Certain tones containing a DMRS patternmay indicate that the URLLC data is present. In an aspect, the URLLCdata punctures eMBB data in the PDSCH.

FIG. 16 is a flowchart 1600 of a method of wireless communication. Themethod may be performed by a UE (e.g., the UE 104, 350, 404, theapparatus 2002, 2002′). At 1602 a UE receives, from a base station, aURLLC indicator indicating a set of UL URLLC resources for transmittingURLLC data. For example, the UE 104, 350, 404, (e.g., apparatus 2002,2002′) may receive, from the base station 102, 310, 402, 1802, 1802′, aURLLC indicator 1008 indicating a set of UL URLLC resources fortransmitting URLLC data 1006, as described in connection with theexample of FIG. 10.

At 1604, the UE generates a set of resource blocks including URLLC data.For example, the UE 104, 350, 404 may generate a set of resource blocksincluding URLLC data 1006, as described in connection with the exampleof FIG. 10.

At 1606, the UE sends, to the base station, the set of resource blocksincluding the URLLC data within the indicated set of UL URLLC resources.For example, the UE 104, 350, 404 sends, to the base station 102, 310,402, the set of resource blocks including the URLLC data 1006 within theindicated set of UL URLLC resources. (See FIG. 10.) In some aspects, anindicator may be sent regardless of the presence of URLLC data. Forexample, a URLLC indicator may be sent periodically. In other aspects, aURLLC indicator may be sent only when URLLC data is present.

In an aspect, the URLLC indicator 1008 may be frequency divisionmultiplexed with a PDSCH 1004. (See FIG. 10.)

In an aspect, the URLLC indicator 1008 may be frequency divisionmultiplexed with a PDCCH 1110. (See FIG. 10.)

In an aspect, the URLLC indicator 1008 does not overlap with the PDCCH.

In an aspect, the URLLC indicator 1008 may be frequency divisionmultiplexed with a PDCCH 1010 in the subset of the set of resourceblocks and/or frequency division multiplexed with a PDSCH 1004 in thesubset of the set of resource blocks.

In an aspect, the URLLC indicator 1008 may be embedded in the URLLC data1006 (1014).

In an aspect, the URLLC indicator 1008 and the URLLC data 1006 may havea comb subcarrier structure.

In an aspect, the URLLC indicator 1008 may be received in a URLLCindicator channel with DMRS. In an aspect, a wireless communicationdevice may check to determine whether certain tones contain a DMRSpattern. Certain tones containing a DMRS pattern may indicate that theURLLC data is present. In an aspect, the URLLC data punctures eMBB datain the PDSCH.

FIG. 17 is a flowchart 1700 of a method of wireless communication. Themethod may be performed by a base station (e.g., the base station 102,310, 402, the apparatus 1802, 1802′). At 1702, a base station sends, toa UE, a URLLC indicator indicating a set of UL URLLC resources fortransmitting URLLC data. For example, the base station 102, 310, 402,1802, 1802′ sends, to a UE 104, 350, 404, the apparatus 2002, 2002′, aURLLC indicator 608 indicating a set of UL URLLC resources fortransmitting URLLC data 1006. (See FIG. 10.)

At 1704, the base station receives, from the UE, a set of resourceblocks including URLLC data, the received URLLC data being receivedwithin the indicated set of UL URLLC resources. For example, the basestation 102, 310, 402, 1802, 1802′ receives, from the UE 104, 350, 404,(e.g., apparatus 2002, 2002′) a set of resource blocks including URLLCdata 1006. The received URLLC data 1006 may be received within theindicated set of UL URLLC resources. (See FIG. 10.) In some aspects, anindicator may be received regardless of the presence of URLLC data. Forexample, a URLLC indicator may be received periodically. In otheraspects, a URLLC indicator may be received only when URLLC data ispresent.

In an aspect, the URLLC indicator 1008 does not overlap with the eMBBdata 1002 (1016).

In an aspect, the URLLC indicator 1008 may indicate to the at least oneUE 104, 350, 404 that the URLLC data 1006 is within at least one of aset of symbols or a set of subcarriers of the set of resource blocks.

In an aspect, the URLLC indicator 1008 may be frequency divisionmultiplexed with a PDCCH 1010 in the subset of the set of resourceblocks and/or frequency division multiplexed with a PDSCH 1004 in thesubset of the set of resource blocks.

In an aspect, the URLLC indicator 1008 may be embedded in the URLLC data1006.

In an aspect, the URLLC indicator 1008 and the URLLC data 1006 may havea comb subcarrier structure.

In an aspect, the URLLC indicator 1008 may be sent in a URLLC indicatorchannel with DMRS. In an aspect, a wireless communication device maycheck to determine whether certain tones contain a DMRS pattern. Certaintones containing a DMRS pattern may indicate that the URLLC data ispresent. In an aspect, the URLLC data punctures eMBB data in the PDSCH.

FIG. 18 is a conceptual data flow diagram 1800 illustrating the dataflow between different means/components in an exemplary apparatus 1802.The apparatus may be a base station (e.g., base station 102, 180, 310,402). The apparatus includes a component 1804 that that receives signals1852 from a UE 1850 (e.g., UE 104, 350, 404, the apparatus 2002, 2002′),a component 1806 that generates a set of resource blocks including atleast one of eMBB data 602 or URLLC data 606 in a PDSCH 604. The URLLCdata 606 may be one of embedded in the eMBB data 602 or unembedded inthe eMBB data 602 based on the signals 1854, a component 1808 thatgenerates a URLLC indicator 608 indicating whether the set of resourceblocks includes the URLLC data 606 based on received signals 1856, acomponent 1810 that sends, to at least one UE 104, 350, 404, the URLLCindicator 608 and the set of resource blocks including the at least oneof the eMBB data 602 or the URLLC data 606, the URLLC indicator 608being sent embedded within the URLLC data 606 or being sent separatefrom the URLLC data 606 within DCI of a PDCCH. In an aspect, the URLLCindicator 608 may be within a separate indicator channel, and acomponent 1812 that transmits signals 1864 based on signals 1862 fromthe control component 1810.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 12. Assuch, each block in the aforementioned flowcharts of FIG. 12 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 19 is a diagram 1900 illustrating an example of a hardwareimplementation for an apparatus 1802′ employing a processing system1914. The processing system 1914 may be implemented with a busarchitecture, represented generally by the bus 1924. The bus 1924 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1914 and the overalldesign constraints. The bus 1924 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 1904, the components 1804, 1806, 1808, 1810, 1812, andthe computer-readable medium/memory 1906. The bus 1924 may also linkvarious other circuits such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The processing system 1914 may be coupled to a transceiver 1910. Thetransceiver 1910 is coupled to one or more antennas 1920. Thetransceiver 1910 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1910 receives asignal from the one or more antennas 1920, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1914, specifically the reception component 1804. Inaddition, the transceiver 1910 receives information from the processingsystem 1914, specifically the transmission component 1812, and based onthe received information, generates a signal to be applied to the one ormore antennas 1920. The processing system 1914 includes a processor 1904coupled to a computer-readable medium/memory 1906. The processor 1904 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 1906. The software, whenexecuted by the processor 1904, causes the processing system 1914 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 1906 may also be used forstoring data that is manipulated by the processor 1904 when executingsoftware. The processing system 1914 further includes at least one ofthe components 1804, 1806, 1808, 1810, 1812. The components may besoftware components running in the processor 1904, resident/stored inthe computer readable medium/memory 1906, one or more hardwarecomponents coupled to the processor 1904, or some combination thereof.The processing system 1914 may be a component of the base station 310and may include the memory 376 and/or at least one of the TX processor316, the RX processor 370, and the controller/processor 375.

In one configuration, the apparatus 1802/1802′ for wirelesscommunication includes means for generating a set of resource blocksincluding at least one of eMBB data or URLLC data in a PDSCH. The URLLCdata may be one of embedded in the eMBB data or unembedded in the eMBBdata, means for generating a URLLC indicator indicating whether the setof resource blocks includes the URLLC data, a means for sending, to atleast one UE, the URLLC indicator and the set of resource blocksincluding the at least one of the eMBB data or the URLLC data, the URLLCindicator being sent embedded within the URLLC data or being sentseparate from the URLLC data within downlink control information (DCI)of a physical downlink control channel (PDCCH). In an aspect, the URLLCindicator 608 may be within a separate indicator channel. Theaforementioned means may be one or more of the aforementioned componentsof the apparatus 1802 and/or the processing system 1914 of the apparatus1802′ configured to perform the functions recited by the aforementionedmeans. As described supra, the processing system 1914 may include the TXProcessor 316, the RX Processor 370, and the controller/processor 375.As such, in one configuration, the aforementioned means may be the TXProcessor 316, the RX Processor 370, and the controller/processor 375configured to perform the functions recited by the aforementioned means.

FIG. 20 is a conceptual data flow diagram 2000 illustrating the dataflow between different means/components in an exemplary apparatus 2002.The apparatus may be a UE (e.g., UE 104, 350, 404). The apparatusincludes a component 2004 that receives signals 2052 from the basestation 2050 (e.g., base station 102, 180, 310, 402, the apparatus 1802,1802′), a component 2006 that receives a set of resource blocks from abase station 102, 310, 402 including at least one of eMBB data or URLLCdata in a PDSCH, a component 2008 that receive a URLLC indicator 608from the base station 102, 310, 402, the URLLC indicator 608 beingreceived embedded within the URLLC data 606 or being received separatefrom the URLLC data 606 within DCI of a PDCCH. In an aspect, the URLLCindicator 608 may be within a separate indicator channel, the URLLCindicator 608 indicating whether the set of resource blocks includes theURLLC data 606. The URLLC data 606 may be embedded in eMBB data 602 orunembedded in eMBB data 602, a component 2010 that determines, based onthe URLLC indicator 608, whether the set of resource blocks includes theURLLC data 606. The determination 2060 from the determine component 2010and the received resource blocks 2062 may be passed to the processingcomponent 2012 which may processes, based on the URLLC indicator 608,the received set of resource blocks including the at least one of theeMBB data 602 or the URLLC data 606. The processing component 2012 mayfurther control transmissions 2066 to the base station 2050 using atransmission control signal 2064.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 13. Assuch, each block in the aforementioned flowcharts of FIG. 13 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 21 is a diagram 2100 illustrating an example of a hardwareimplementation for an apparatus 2002′ employing a processing system2114. The processing system 2114 may be implemented with a busarchitecture, represented generally by the bus 2124. The bus 2124 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2114 and the overalldesign constraints. The bus 2124 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 2104, the components 2004, 2006, 2008, 2010, 2012,2014, and the computer-readable medium/memory 2106. The bus 2124 mayalso link various other circuits such as timing sources, peripherals,voltage regulators, and power management circuits, which are well knownin the art, and therefore, will not be described any further.

The processing system 2114 may be coupled to a transceiver 2110. Thetransceiver 2110 is coupled to one or more antennas 2120. Thetransceiver 2110 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 2110 receives asignal from the one or more antennas 2120, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2114, specifically the reception component 2004. Inaddition, the transceiver 2110 receives information from the processingsystem 2114, specifically the transmission component 2014, and based onthe received information, generates a signal to be applied to the one ormore antennas 2120. The processing system 2114 includes a processor 2104coupled to a computer-readable medium/memory 2106. The processor 2104 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 2106. The software, whenexecuted by the processor 2104, causes the processing system 2114 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 2106 may also be used forstoring data that is manipulated by the processor 2104 when executingsoftware. The processing system 2114 further includes at least one ofthe components 2004, 2006, 2008, 2010, 2012, and 2014. The componentsmay be software components running in the processor 2104,resident/stored in the computer readable medium/memory 2106, one or morehardware components coupled to the processor 2104, or some combinationthereof. The processing system 2114 may be a component of the UE 350 andmay include the memory 360 and/or at least one of the TX processor 368,the RX processor 356, and the controller/processor 359.

In one configuration, the apparatus 2002/2002′ for wirelesscommunication may include means for receiving a set of resource blocksfrom a base station includes at least one of eMBB data or URLLC data ina PDSCH, means for receiving a URLLC indicator from the base station,the URLLC indicator being received embedded within the URLLC data orbeing received separate from the URLLC data within DCI of a PDCCH. In anaspect, the URLLC indicator 608 may be within a separate indicatorchannel, the URLLC indicator indicating whether the set of resourceblocks includes the URLLC data. The URLLC data may be embedded in eMBBdata or unembedded in eMBB data, means for determining, based on theURLLC indicator, whether the set of resource blocks includes the URLLCdata, and means for processing, based on the URLLC indicator, thereceived set of resource blocks including the at least one of the eMBBdata or the URLLC data.

The aforementioned means may be one or more of the aforementionedcomponents of the apparatus 2002 and/or the processing system 2114 ofthe apparatus 2002′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 2114 mayinclude the TX Processor 368, the RX Processor 356, and thecontroller/processor 359. As such, in one configuration, theaforementioned means may be the TX Processor 368, the RX Processor 356,and the controller/processor 359 configured to perform the functionsrecited by the aforementioned means.

FIG. 22 is a conceptual data flow diagram 2200 illustrating the dataflow between different means/components in an exemplary apparatus 2202.The apparatus may be a UE (e.g., UE 104, 350, 404, the apparatus 2202,2202′). The apparatus includes a component 2204 that that receivessignals 2252 from a base station 2250 (e.g., base station 102, 180, 310,402, the apparatus 2402, 2402′), a component 2206 that generates a setof resource blocks including URLLC data based on the signals 2254, acomponent 2208 that generates generating a URLLC indicator indicatingthat the URLLC data is in a subset of the set of resource blocks basedon received signals 2256, a component 1810 that sends, to a basestation, the URLLC indicator and the set of resource blocks includingthe URLLC data 2258 using signal 2262 and through transmission component2212 which transmits to the base station using signal 2264.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 14. Assuch, each block in the aforementioned flowcharts of FIG. 14 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 23 is a diagram 2300 illustrating an example of a hardwareimplementation for an apparatus 2202′ employing a processing system2314. The processing system 2314 may be implemented with a busarchitecture, represented generally by the bus 2324. The bus 2324 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2314 and the overalldesign constraints. The bus 2324 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 2304, the components 2204, 2206, 2208, and thecomputer-readable medium/memory 2306. The bus 2324 may also link variousother circuits such as timing sources, peripherals, voltage regulators,and power management circuits, which are well known in the art, andtherefore, will not be described any further.

The processing system 2314 may be coupled to a transceiver 2310. Thetransceiver 2310 is coupled to one or more antennas 2320. Thetransceiver 2310 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 2310 receives asignal from the one or more antennas 2320, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2314, specifically the reception component 2204. Inaddition, the transceiver 2310 receives information from the processingsystem 2314, specifically the transmission component 2212, and based onthe received information, generates a signal to be applied to the one ormore antennas 2320. The processing system 2314 includes a processor 2304coupled to a computer-readable medium/memory 2306. The processor 2304 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 2306. The software, whenexecuted by the processor 2304, causes the processing system 2314 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 2306 may also be used forstoring data that is manipulated by the processor 2304 when executingsoftware. The processing system 2314 further includes at least one ofthe components 2204, 2206, 2208, 2210, 2212. The components may besoftware components running in the processor 2304, resident/stored inthe computer readable medium/memory 2306, one or more hardwarecomponents coupled to the processor 2304, or some combination thereof.The processing system 2314 may be a component of the UE 350 and mayinclude the memory 360 and/or at least one of the TX processor 368, theRX processor 356, and the controller/processor 359.

In one configuration, the apparatus 2202/2202′ for wirelesscommunication includes means for means for generating a set of resourceblocks including URLLC data, means for generating a URLLC indicatorindicating that the URLLC data is in a subset of the set of resourceblocks, and means for sending, to a base station, the URLLC indicatorand the set of resource blocks including the URLLC data. Theaforementioned means may be one or more of the aforementioned componentsof the apparatus 2202 and/or the processing system 2314 of the apparatus2202′ configured to perform the functions recited by the aforementionedmeans. As described supra, the processing system 2314 may include the TXProcessor 368, the RX Processor 356, and the controller/processor 359.As such, in one configuration, the aforementioned means may be the TXProcessor 368, the RX Processor 356, and the controller/processor 359configured to perform the functions recited by the aforementioned means.

FIG. 24 is a conceptual data flow diagram 2400 illustrating the dataflow between different means/components in an exemplary apparatus 2402.The apparatus may be a base station (e.g., base station 102, 180, 310,402, the apparatus 2402, 2402′). The apparatus includes a component 2404that receives signals 2452 from a UE 2450 (e.g., UE 104, 350, 404, theapparatus 2402, 2402′), a component 2406 that that receives a set ofresource blocks 2454 from a UE, a component 2408 that receives a URLLCindicator 2456 from the UE, a component 2410 that determines, based onthe URLLC indicator 2058, that the set of resource blocks includes URLLCdata. The determination 2460 from the determine component 2410 and thereceived resource blocks 2462 may be passed to the processing component2412 which may control transmissions 2466 to the UE 2450 using atransmission control signal 2464.

The apparatus may include additional components that perform each of theblocks of the algorithm in the aforementioned flowcharts of FIG. 15. Assuch, each block in the aforementioned flowcharts of FIG. 15 may beperformed by a component and the apparatus may include one or more ofthose components. The components may be one or more hardware componentsspecifically configured to carry out the stated processes/algorithm,implemented by a processor configured to perform the statedprocesses/algorithm, stored within a computer-readable medium forimplementation by a processor, or some combination thereof.

FIG. 25 is a diagram 2500 illustrating an example of a hardwareimplementation for an apparatus 2402′ employing a processing system2514. The processing system 2514 may be implemented with a busarchitecture, represented generally by the bus 2524. The bus 2524 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2514 and the overalldesign constraints. The bus 2524 links together various circuitsincluding one or more processors and/or hardware components, representedby the processor 2504, the components 2404, 2406, 2408, 2410, 2412, 2414and the computer-readable medium/memory 2506. The bus 2524 may also linkvarious other circuits such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The processing system 2514 may be coupled to a transceiver 2510. Thetransceiver 2510 is coupled to one or more antennas 2520. Thetransceiver 2510 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 2510 receives asignal from the one or more antennas 2520, extracts information from thereceived signal, and provides the extracted information to theprocessing system 2514, specifically the reception component 2404. Inaddition, the transceiver 2510 receives information from the processingsystem 2514, specifically the transmission component 2414, and based onthe received information, generates a signal to be applied to the one ormore antennas 2520. The processing system 2514 includes a processor 2504coupled to a computer-readable medium/memory 2506. The processor 2504 isresponsible for general processing, including the execution of softwarestored on the computer-readable medium/memory 2506. The software, whenexecuted by the processor 2504, causes the processing system 2514 toperform the various functions described supra for any particularapparatus. The computer-readable medium/memory 2506 may also be used forstoring data that is manipulated by the processor 2504 when executingsoftware. The processing system 2514 further includes at least one ofthe components 2404, 2406, 2408, 2410, 2412, 2414. The components may besoftware components running in the processor 2504, resident/stored inthe computer readable medium/memory 2506, one or more hardwarecomponents coupled to the processor 2504, or some combination thereof.The processing system 2514 may be a component of the base station 310and may include the memory 376 and/or at least one of the TX processor316, the RX processor 370, and the controller/processor 375.

In one configuration, the apparatus 2402/2402′ for wirelesscommunication includes means for means for receiving a set of resourceblocks from a user equipment (UE), means for receiving a URLLC indicatorfrom the UE, and mans for determining, based on the URLLC indicator,that a subset of the set of resource blocks includes URLLC data. Theaforementioned means may be one or more of the aforementioned componentsof the apparatus 2402 and/or the processing system 2514 of the apparatus2402′ configured to perform the functions recited by the aforementionedmeans. As described supra, the processing system 2514 may include the TXProcessor 316, the RX Processor 370, and the controller/processor 375.As such, in one configuration, the aforementioned means may be the TXProcessor 316, the RX Processor 370, and the controller/processor 375configured to perform the functions recited by the aforementioned means.

As described herein, various aspects relate to uplink or downlinkindications. The uplink or downlink indications may be URLLCindications, i.e., a URLLC indicator. Accordingly, in some aspects, theURLLC indicator may be an uplink URLLC indicator and in other aspects,the URLLC indicator may be a downlink URLLC indicator. The downlinkindicator may be transmitted from a base station to a UE. The uplinkindicator may be transmitted from a UE to a base station. In an aspect,a downlink indicator may be in DCI. A downlink indicator may be a postindication, e.g., indicating in a subsequent slot whether the URLCC datais present or not. Additionally, a downlink indicator may be configuredto be a wideband indication or a sub-band indication (e.g., up to 2sub-bands) indication. Furthermore, a downlink indicator may beconfigured to indicate one or more symbols by configuring the monitoringperiodicity. In an aspect, a uplink indicator may use one or more of theformats described herein with respect to downlink indicators. FIGS. 5 to11 may provide various formats that may be used with respect to uplinkor downlink indications. In some aspects, downlink indications mayrelate to one or more aspects of FIG. 8.

In an aspect, a URLLC and an eMBB may be transmitted based on differenttransmission duration. For example, eMBB long (slot based) or URLLCshort (mini-slot based).

Dynamic resource sharing between URLLC and eMBB may be supported.

In an aspect, URLLC may be pre-empted/puncture resource occupied byon-going eMBB.

In an aspect, URLLC an indication may be supported.

In an aspect, an indication of URLLC preemption may be sent to eMBB UEregarding the impacted eMBB resource to facilitate eMBB UE demodulationand decoding of the current transmission and subsequent retransmissions.

In an aspect, an indication channel may use a current indication (e.g.,current with respect to URLLC traffic). In an aspect, an indicationchannel may use post indication.

It is understood that the specific order or hierarchy of blocks in theprocesses/flowcharts disclosed is an illustration of exemplaryapproaches. Based upon design preferences, it is understood that thespecific order or hierarchy of blocks in the processes/flowcharts may berearranged. Further, some blocks may be combined or omitted. Theaccompanying method claims present elements of the various blocks in asample order, and are not meant to be limited to the specific order orhierarchy presented.

In an aspect, an apparatus for wireless communication, may include amemory and at least one processor coupled to the memory and configuredto receive a set of resource blocks from a base station includes atleast one of eMBB data or URLLC data in a PDSCH, receive a URLLCindicator from the base station, the URLLC indicator being receivedembedded within the URLLC data or being received separate from the URLLCdata within DCI of a PDCCH. In an aspect, the URLLC indicator 608 may bewithin a separate indicator channel, the URLLC indicator indicatingwhether the set of resource blocks includes the URLLC data. The URLLCdata may be embedded in eMBB data or unembedded in eMBB data, determine,based on the URLLC indicator, whether the set of resource blocksincludes the URLLC data, and processing the set of resource blocks basedon a result of determining whether the set of resource blocks includesthe URLLC data.

In an aspect, an apparatus for wireless communication, may include amemory and at least one processor coupled to the memory and configuredto generate a set of resource blocks including at least one of eMBB dataor URLLC data in a PDSCH. The URLLC data may be one of embedded in theeMBB data or unembedded in the eMBB data, generate a URLLC indicatorindicating whether the set of resource blocks includes the URLLC data,and send, to at least one UE, the URLLC indicator and the set ofresource blocks including the at least one of the eMBB data or the URLLCdata, the URLLC indicator being sent embedded within the URLLC data orbeing sent separate from the URLLC data within DCI of a PDCCH. In anaspect, the URLLC indicator 608 may be within a separate indicatorchannel.

In an aspect, the URLLC indicator may indicate whether the set ofresource blocks includes the at least part of the URLLC data. The URLLCdata may be at least partially embedded in eMBB data or unembedded ineMBB data. The UE may be configured to determine, based on the URLLCindicator, whether the set of resource blocks includes at least part ofthe URLLC data.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” The word “exemplary” is used hereinto mean “serving as an example, instance, or illustration.” Any aspectdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects. Unless specifically statedotherwise, the term “some” refers to one or more. Combinations such as“at least one of A, B, or C,” “one or more of A, B, or C,” “at least oneof A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or anycombination thereof” include any combination of A, B, and/or C, and mayinclude multiples of A, multiples of B, or multiples of C. Specifically,combinations such as “at least one of A, B, or C,” “one or more of A, B,or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and“A, B, C, or any combination thereof” may be A only, B only, C only, Aand B, A and C, B and C, or A and B and C, where any such combinationsmay contain one or more member or members of A, B, or C. All structuraland functional equivalents to the elements of the various aspectsdescribed throughout this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the claims.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe claims. The words “module,” “mechanism,” “element,” “device,” andthe like may not be a substitute for the word “means.” As such, no claimelement is to be construed as a means plus function unless the elementis expressly recited using the phrase “means for.”

1-24. (canceled)
 25. A method of wireless communication at a userequipment (UE), comprising: monitoring for a preemption indication basedon a downlink configuration, the downlink configuration indicating howgranular the preemption indication identifies preemption in a data spacein terms of resources that are configurable at different granularities;receiving, from a base station at a first time on shared downlinkresources, a data transmission comprising first data associated with afirst type of wireless communication; receiving, from the base stationat a second time subsequent to the first time, the preemption indicationin a group common physical downlink control channel (PDCCH);determining, based on the preemption indication, whether at least aportion of the shared downlink resources occupied by the first data ispreempted for use by the UE, the preemption comprising second dataassociated with a second type of wireless communication different fromthe first type of wireless communication puncturing resources occupiedby the first data within the data transmission; and decoding the firstdata when the at least a portion of the shared downlink resources is notpreempted by the second data.
 26. The method of claim 25, furthercomprising refraining from decoding at least a portion of the first datathat occupies resources corresponding to the at least a portion of theshared downlink resources when the at least a portion of the shareddownlink resources is preempted by the second data.
 27. The method ofclaim 25, wherein the shared downlink resources includes a first portionthat is preempted by the second data and a second portion that is notpreempted by the second data, further comprising: refraining fromdecoding a first portion of the first data that occupies resourcescorresponding to the first portion of the shared downlink resources thatis preempted; and decoding a second portion of the first data thatoccupies resources corresponding to the second portion of the shareddownlink resources that is not preempted.
 28. The method of claim 25,wherein the first data associated with the first type of wirelesscommunication corresponds to enhanced mobile broadband (eMBB) data andthe second data associated with the second type of wirelesscommunication corresponds to ultra-reliable low-latency communication(URLLC) data.
 29. The method of claim 25, wherein the group common PDCCHincludes downlink control information (DCI), wherein the receiving thepreemption indication comprises receiving the preemption indication inat least a portion of the DCI.
 30. The method of claim 25, wherein thepreemption indication occupies one or more symbols in a mini-slot. 31.The method of claim 25, wherein the preemption indication occupies oneor more symbols at every predetermined number of mini-slots.
 32. Themethod of claim 25, wherein the preemption indication is included in thegroup common PDCCH across a full bandwidth.
 33. The method of claim 25,wherein the preemption indication is included in the group common PDCCHacross one or more sub-bands of a bandwidth.
 34. The method of claim 25,wherein the downlink configuration indicates a periodicity of thepreemption indication.
 35. The method of claim 25, further comprisingreceiving, from the base station, the downlink configuration,dynamically, via downlink control information (DCI) signaling.
 36. Themethod of claim 25, further comprising receiving, from the base station,the downlink configuration, semi-statically, via radio resource control(RRC) signaling.
 37. The method of claim 25, wherein receiving the datatransmission comprises receiving a first subframe that includes the datatransmission, wherein the receiving the preemption indication comprisesreceiving a second subframe that follows the first subframe, furthercomprising transmitting, to the base station, an uplink short burst(ULSB) that is located between the first subframe and the secondsubframe.
 38. The method of claim 25, wherein the receiving the datatransmission comprises receiving, from the base station, a physicaldownlink shared channel (PDSCH) that includes the data transmission inat least a portion of the PDSCH, wherein the first data and the seconddata coexist within the at least the portion of the PDSCH, and whereinthe data space corresponds to the PDSCH.
 39. The method of claim 38,wherein the second data occupies resources that puncture one or moretime resources occupied by the first data within the shared downlinkresources at a preconfigured granularity according to the downlinkconfiguration.
 40. The method of claim 38, wherein the second dataoccupies resources that puncture one or more frequency resourcesoccupied by the first data within the shared downlink resources at apreconfigured granularity according to the downlink configuration. 41.The method of claim 38, wherein the downlink configuration indicatesthat the preemption indication is separate from the data transmissionwithin the PDSCH.
 42. The method of claim 25, wherein each of thedifferent granularities corresponds to a different time resource size.43. The method of claim 25, wherein each of the different granularitiescorresponds to a different frequency resource size.
 44. An apparatus forwireless communication at a user equipment (UE), comprising: a memory; atransceiver; and at least one processor coupled to the memory and thetransceiver, the at least one processor being configured to executeinstructions stored on the memory that cause the UE to: monitor for apreemption indication based on a downlink configuration, the downlinkconfiguration indicating how granular the preemption indicationidentifies preemption in a data space in terms of resources that areconfigurable at different granularities; receive, from a base station ata first time on shared downlink resources, via the transceiver, a datatransmission comprising first data associated with a first type ofwireless communication; receive, from the base station at a second timesubsequent to the first time, via the transceiver, the preemptionindication in a group common physical downlink control channel (PDCCH);determine, based on the preemption indication, whether at least aportion of the shared downlink resources occupied by the first data ispreempted for use by the UE, the preemption comprising second dataassociated with a second type of wireless communication different fromthe first type of wireless communication puncturing resources occupiedby the first data within the data transmission; and decode the firstdata when the at least a portion of the shared downlink resources is notpreempted by the second data.
 45. The apparatus of claim 44, furthercomprising refraining from decoding at least a portion of the first datathat occupies resources corresponding to the at least a portion of theshared downlink resources when the at least a portion of the shareddownlink resources is preempted by the second data.
 46. The apparatus ofclaim 44, wherein the shared downlink resources includes a first portionthat is preempted by the second data and a second portion that is notpreempted by the second data, further comprising: refraining fromdecoding a first portion of the first data that occupies resourcescorresponding to the first portion of the shared downlink resources thatis preempted; and decoding a second portion of the first data thatoccupies resources corresponding to the second portion of the shareddownlink resources that is not preempted.
 47. The apparatus of claim 44,wherein the group common PDCCH includes downlink control information(DCI), wherein the receiving the preemption indication comprisesreceiving the preemption indication in at least a portion of the DCI.48. A method of wireless communication at a base station, the methodcomprising: transmitting, to one or more user equipment (UE), a downlinkconfiguration that indicates how granular a preemption indicationidentifies preemption in a data space in terms of resources that areconfigurable at different granularities; transmitting, to the one ormore UEs at a first time on shared downlink resources, a datatransmission comprising first data associated with a first type ofwireless communication; and transmitting, to the one or more UEs at asecond time subsequent to the first time, the preemption indication in agroup common physical downlink control channel (PDCCH), wherein thepreemption indication indicates whether at least a portion of the shareddownlink resources occupied by the first data is preempted for use bythe UE, the preemption comprising second data associated with a secondtype of wireless communication different from the first type of wirelesscommunication puncturing resources occupied by the first data within thedata transmission.
 49. The method of claim 48, wherein the group commonPDCCH includes downlink control information (DCI), wherein thetransmitting the preemption indication comprises transmitting thepreemption indication in at least a portion of the DCI.
 50. The methodof claim 48, further comprising transmitting, to the one or more UEs,the downlink configuration, dynamically, via downlink controlinformation (DCI) signaling.
 51. The method of claim 48, furthercomprising transmitting, to the one or more UEs, the downlinkconfiguration, semi-statically, via radio resource control (RRC)signaling.
 52. The method of claim 48, wherein transmitting the datatransmission comprises transmitting a first subframe that includes thedata transmission, wherein the transmitting the preemption indicationcomprises transmitting a second subframe that follows the firstsubframe, further comprising receiving, from at least one of the one ormore UEs, an uplink short burst (ULSB) that is located between the firstsubframe and the second subframe.
 53. The method of claim 48, whereinthe transmitting the data transmission comprises transmitting, to theone or more UEs, a physical downlink shared channel (PDSCH) thatincludes the data transmission in at least a portion of the PDSCH,wherein the first data and the second data coexist within the at leastthe portion of the PDSCH, and wherein the data space corresponds to thePDSCH.
 54. An apparatus for wireless communication at a base station,comprising: a memory; a transceiver; and at least one processor coupledto the memory and the transceiver, the at least one processor beingconfigured to execute instructions stored on the memory that cause thebase station to: transmit, to one or more user equipment (UEs), via thetransceiver, a downlink configuration that indicates how granular apreemption indication identifies preemption in a data space in terms ofresources that are configurable at different granularities; transmit, tothe one or more UEs at a first time on shared downlink resources, viathe transceiver, a data transmission comprising first data associatedwith a first type of wireless communication; and transmit, to the one ormore UEs at a second time subsequent to the first time, via thetransceiver, the preemption indication in a group common physicaldownlink control channel (PDCCH), wherein the preemption indicationindicates whether at least a portion of the shared downlink resourcesoccupied by the first data is preempted for use by the UE, thepreemption comprising second data associated with a second type ofwireless communication different from the first type of wirelesscommunication puncturing resources occupied by the first data within thedata transmission.